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
A clear and concise description of what the problem is, e.g. I'm always frustrated when [...].
Currently, the query hashcode is generated based on the query shape that contains field name and field datatype information.
The query hashcode should also be a function of index name, tenant_id/WLM group, resource group, etc.
We can also consider enhancing the query shape to include range width to take in to account a wide range vs a narrow range (Eg: 1 day vs 1 year).
These changes will ensure better grouping of queries and will enable us to see query groups per tenant_id/resource group in the future.
What solution would you like?
A clear and concise description of what you want to happen.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any 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?
A clear and concise description of what the problem is, e.g. I'm always frustrated when [...].
Currently, the query hashcode is generated based on the query shape that contains field name and field datatype information.
The query hashcode should also be a function of index name, tenant_id/WLM group, resource group, etc.
We can also consider enhancing the query shape to include range width to take in to account a wide range vs a narrow range (Eg: 1 day vs 1 year).
These changes will ensure better grouping of queries and will enable us to see query groups per tenant_id/resource group in the future.
What solution would you like?
A clear and concise description of what you want to happen.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: