You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The query ID for pull queries is made static i.e. the same for all pull queries on the same sink. For error logging purposes, this is not informative. At the moment the queryId is returned in the response, so users are able to filter the processing log to get just the errors for their invocation. But if all Pull queries have the same query ID, users cannot pinpoint to the specific query that might have failed.
Background information: This change was made as part of #3708
Describe the solution you'd like
We want to change this back to being a unique ID per pull query. Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The query ID for pull queries is made static i.e. the same for all pull queries on the same sink. For error logging purposes, this is not informative. At the moment the queryId is returned in the response, so users are able to filter the processing log to get just the errors for their invocation. But if all Pull queries have the same query ID, users cannot pinpoint to the specific query that might have failed.
Background information: This change was made as part of #3708
Describe the solution you'd like
We want to change this back to being a unique ID per pull query.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: