Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add an unified storage class for data plugin #7701
Add an unified storage class for data plugin #7701
Changes from all commits
5750155
87ab64c
3b27524
29f90c5
90ebecd
54b8fb2
36ed793
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i do like this structure. it makes it easier to not use
opensearchDashboards.
and just pass the keyThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems pretty advanced hah nice. and only has functionality for recents. or do you mean configurable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you explain the decision to go with
query_
it makes sense to me but do we have to make it more specific to avoid potential collisions? did we look into the decision of the name of the keyssense
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea not sure about the meaning of "ssense" , but i think "_query" makes sense for saving recent query here? They full key is
opensearch_dashboards.query_1723753938175
, the numbers followed are the timetamp, i think it will avoid collisions?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here is the current saved query saved object.
I think we should follow the same format and property names as the saved query.
you have query, but i would rename dataRange to timeFilter and i would include filters as well.
time could probaby could be
submitted_at
should we consider workspaces @ashwin-pc ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so inside the
onQueryBarSubmit
function, we only get time range as props. But time filter includes both time range and refresh interval. So do you think we need to include refresh interval and the filters here?