-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add logging to query #17498
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
poachable
punted-for-3.1
type-enhancement
Milestone
Comments
@smitpatel to point to the places where we need to log. |
Also consider #12662 |
|
Note from team discussion: make sure to add the no-ordering warnings back. They don't need to be provider-specific. See #19331 |
Note from API Review: Re-use the previous EventIds as much as possible |
Cleaning up tests which are verifying error messages should be a good start. |
smitpatel
added a commit
that referenced
this issue
Aug 4, 2020
Part of #17498 Added messages - Starting query compilation - Navigation included - Skip/Take without order by (infra is in core but providers use to generate the warning) - First without order by or predicate (infra is in core but providers use to generate the warning) Removed messages - Include ignored (they get removed due to automatic pruning based on expression tree visitation - Obsolete exception with aggregate operator in relational. We logged that when doing client eval of aggregate operation - Optimized query model - there is no more optimization phase. Other fixes - Don't log parameter values in Cosmos when sensitive data logging is not enabled.
Merged
smitpatel
added a commit
that referenced
this issue
Aug 4, 2020
Part of #17498 Added messages - Starting query compilation - Navigation included - Skip/Take without order by (infra is in core but providers use to generate the warning) - First without order by or predicate (infra is in core but providers use to generate the warning) Removed messages - Include ignored (they get removed due to automatic pruning based on expression tree visitation - Obsolete exception with aggregate operator in relational. We logged that when doing client eval of aggregate operation - Optimized query model - there is no more optimization phase. Other fixes - Don't log parameter values in Cosmos when sensitive data logging is not enabled.
ghost
pushed a commit
that referenced
this issue
Aug 4, 2020
Part of #17498 Added messages - Starting query compilation - Navigation included - Skip/Take without order by (infra is in core but providers use to generate the warning) - First without order by or predicate (infra is in core but providers use to generate the warning) Removed messages - Include ignored (they get removed due to automatic pruning based on expression tree visitation - Obsolete exception with aggregate operator in relational. We logged that when doing client eval of aggregate operation - Optimized query model - there is no more optimization phase. Other fixes - Don't log parameter values in Cosmos when sensitive data logging is not enabled.
smitpatel
added a commit
that referenced
this issue
Aug 4, 2020
smitpatel
added a commit
that referenced
this issue
Aug 4, 2020
ghost
pushed a commit
that referenced
this issue
Aug 5, 2020
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
poachable
punted-for-3.1
type-enhancement
The text was updated successfully, but these errors were encountered: