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 [...].
When groups are aggregated across windows we can encounter a scenario where 2 groups have the same id (hashcode). This will lead to 2 rows with the same id on the frontend which is undesirable. We need to aggregate this on the backend when querying the Top N before as part of the API call.
What solution would you like?
A clear and concise description of what you want to happen.
Consider a scenario where we run 3 queries in the same group and have one aggregate query record. When this gets pushed to the local index after the window expires we run 3 queries in the same group again. This might lead to 2 rows in the top queries table with the same group_id . We need to aggregate these groups into one in the API layer before sending to the dashboard.
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 [...].
When groups are aggregated across windows we can encounter a scenario where 2 groups have the same id (hashcode). This will lead to 2 rows with the same id on the frontend which is undesirable. We need to aggregate this on the backend when querying the Top N before as part of the API call.
What solution would you like?
A clear and concise description of what you want to happen.
Consider a scenario where we run 3 queries in the same group and have one aggregate query record. When this gets pushed to the local index after the window expires we run 3 queries in the same group again. This might lead to 2 rows in the top queries table with the same group_id . We need to aggregate these groups into one in the API layer before sending to the dashboard.
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: