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
To support fetching a specific search query record by ID (e.g., for the current detail page or inspecting a historical slow query in the future), we need to add a unique identifier to each search query record.
What solution would you like?
Add an ID field to search query records.
Preferred Approach: Use a randomly generated UUID (via UUID.randomUUID() in Java). UUIDs are 128 bits and provide ~3.4 × 10³⁸ possible values, making the probability of collision effectively zero for our use case.
What alternatives have you considered?
Use the timestamp as the ID: This may fail when multiple queries share the same timestamp.
Use a group hash code: While useful for identifying groups, it is insufficient for distinguishing individual queries within a group at different timestamps.
Generate an ID by hashing the query source and timestamp - this won't avoid ID collision neither
Is your feature request related to a problem?
To support fetching a specific search query record by ID (e.g., for the current detail page or inspecting a historical slow query in the future), we need to add a unique identifier to each search query record.
What solution would you like?
Add an ID field to search query records.
What alternatives have you considered?
Do you have any additional context?
This feature is a prerequisite for opensearch-project/query-insights-dashboards#12
The text was updated successfully, but these errors were encountered: