-
Notifications
You must be signed in to change notification settings - Fork 933
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
[WIP] Async Queries Followup #6966
[WIP] Async Queries Followup #6966
Conversation
ℹ️ Manual Changeset Creation ReminderPlease ensure manual commit for changeset file 6966.yml under folder changelogs/fragments to complete this PR. If you want to use the available OpenSearch Changeset Bot App to avoid manual creation of changeset file you can install it in your forked repository following this link. For more information about formatting of changeset files, please visit OpenSearch Auto Changeset and Release Notes Tool. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/discover-next #6966 +/- ##
========================================================
Coverage ? 66.94%
========================================================
Files ? 3452
Lines ? 68331
Branches ? 11165
========================================================
Hits ? 45745
Misses ? 19966
Partials ? 2620
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
); | ||
// save to cache by title because the id is not unique for temporary index pattern created | ||
indexPatterns.saveToCache(dataSet.title, dataSet); | ||
if (existingIndexPattern) { |
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.
actually we want to create a dataset without an existing index pattern or not. the problem is that we try to get indiceswhen we create the temp index pattern even tho s3 is availabe
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.
we want to check the data source if it's like default or not
if (this.dfCache.get() && this.dfCache.get()?.name !== dataFrame.name) { | ||
scopedIndexPatterns.clearCache(this.dfCache.get()!.name, false); |
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.
Don't need to clearCache()
here right? Think we cleared it in the public
folder
Signed-off-by: Sean Li <[email protected]>
Signed-off-by: Sean Li <[email protected]>
Signed-off-by: Sean Li <[email protected]>
Signed-off-by: Sean Li <[email protected]>
94a8da9
to
471a4ea
Compare
c86e90c
into
opensearch-project:feature/discover-next
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-6966-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c86e90c91e6e61bd610c52a1c11cc88358588560
# Push it to GitHub
git push --set-upstream origin backport/backport-6966-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-6966-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c86e90c91e6e61bd610c52a1c11cc88358588560
# Push it to GitHub
git push --set-upstream origin backport/backport-6966-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x Then, create a pull request where the |
This is not to |
Description
datasource.name
exists before creating dataframeIssues Resolved
#6957
Screenshot
Testing the changes
Changelog
Check List
yarn test:jest
yarn test:jest_integration