Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable access to "non-primary" tables in the response, mainly for cursor feature #85

Closed
liranms opened this issue Apr 4, 2022 · 3 comments

Comments

@liranms
Copy link

liranms commented Apr 4, 2022

Provide ability to access the response that contains other table such as @ExtendedProperties, and QueryResourceConsumption
this is very important for using the kusto database cursor feature which emits the Cursor property on the @ExtendedProperties table
Another interesting aspect is getting the performance metadata on the QueryResourceConsumption for every executed query.
I saw that there was an unused, unexported function named getNonPrimary which hints that you were going to export this feature, currently I just forked and exported it.

@liranms
Copy link
Author

liranms commented Apr 11, 2022

@AsafMah is there a plan to expose this?

@AsafMah
Copy link
Contributor

AsafMah commented Apr 12, 2022

#90 does it, it would soon be completed and will be released in the next version.

@AsafMah
Copy link
Contributor

AsafMah commented Apr 12, 2022

Solved in 0.6.0, feel free to re-open if you have issues.

@AsafMah AsafMah closed this as completed Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants