-
Notifications
You must be signed in to change notification settings - Fork 184
fix: prevent NPE and status inconsistency in index insight #4313
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
base: main
Are you sure you want to change the base?
Conversation
writeIndexInsight( | ||
indexInsight, | ||
tenantId, | ||
ActionListener.wrap(r -> { runWithPrerequisites(tenantId, listener); }, listener::onFailure) |
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.
Why in here we don't save the failure status?
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.
Because if writing the initial GENERATING status fails, the insight will not be stored, so there is no need to update to FAILED status. Also, attempting to save a FAILED status would likely fail for the same reason.
Signed-off-by: shuangli-z <[email protected]>
Signed-off-by: shuangli-z <[email protected]>
… is written Signed-off-by: shuangli-z <[email protected]>
Signed-off-by: shuangli-z <[email protected]>
2011b47
to
04c76bd
Compare
Description
Minor fixes for index insight feature:
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.