-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
fix: View Results Doesn't Match Chart After Refreshing Cache #19540
fix: View Results Doesn't Match Chart After Refreshing Cache #19540
Conversation
25d4280
to
edf9773
Compare
Codecov Report
@@ Coverage Diff @@
## master #19540 +/- ##
=======================================
Coverage 66.55% 66.55%
=======================================
Files 1692 1692
Lines 64801 64806 +5
Branches 6657 6657
=======================================
+ Hits 43128 43132 +4
- Misses 19973 19974 +1
Partials 1700 1700
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
return getChartDataRequest({ | ||
formData: queryFormData, | ||
resultFormat: 'json', | ||
force: !!latestQueryCacheInvalidatedRef.current, | ||
resultType, | ||
ownState, | ||
}) |
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.
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.
As far as I can tell, that force is used for something else, which is tracked in the ExploreViewContainer
.
I also cannot find where in the exploreReducer
that is being modified, but updating that value there will have other consequences
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.
@diegomedina248 I pushed a branch in my repository to fix this issue. discussion welcome.
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.
@zhaoyongjie looks good to me! feel free to close this PR once yours lands here. Thanks
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.
@zhaoyongjie were you indeed opening a PR to resolve this, or just providing some advice/examples?
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.
@rusackas @diegomedina248 I will open a new PR today. Thanks.
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.
opened PR at #19932.
edf9773
to
083ec4b
Compare
Closing in favor of #19932 |
SUMMARY
When the data cache is configured, after a cache invalidation in the explore, the results view is not impacted.
So, if we modify the underlying dataset while using the explore, and we try to invalidate the cache, then the chart correctly displays the new data, but the view results doesn't.
This PR ensures that, after a cache invalidation, both the chart and results reflect the latest data.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
Screen.Recording.2022-04-05.at.20.33.35.mov
After:
new.mov
TESTING INSTRUCTIONS
Ensure that, after cache invalidation, both the chart and data results view reflect the latest data.
ADDITIONAL INFORMATION