-
Notifications
You must be signed in to change notification settings - Fork 4
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
Way to "connect" UBI events with queries #26
Comments
FYI: the |
Are you suggesting that we should have an explicit I can imagine that you would have a typeahead and a global search, and you would want to distingush between these two sources of queries, when generating personlaization inputs or implicit judgement etc... Is |
Question for everyone - is |
Something that can help with naming. What are possible values of @epugh I suppose you mean adding it to queries, since events already has |
If we already have the At least if that does not have any other meaning in the events schema? It feels like a field that should be present for both schemas. |
Thanks for feedback team. I'm going to use |
We should capture |
|
This is now in the plugin, but not in the spec... |
Right now, we don't have an easy straightforward way to link events and queries. There isn't any "glue" other than the
query_id
that links the two and this might not be sufficient.In opensearch-project/user-behavior-insights#34 I want to capture the index(es) that were searched in the UBI queries index, but this might not be appropriate for all use-cases. A more granular approach is likely needed.
We should consider the addition of an
application
field that both queries and events can use to form this linking. Theapplication
can be provided in the query'sext
block, andapplication
can be used in the event schema. Havingapplication
on both would provide a low-level way to connect queries and events.The text was updated successfully, but these errors were encountered: