-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix npe with sql metadata manager polling and empty database #8106
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
Merged
gianm
merged 4 commits into
apache:master
from
clintropolis:sql-metadata-snapshot-npe-fix
Jul 21, 2019
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -950,15 +950,11 @@ public DataSegment map(int index, ResultSet r, StatementContext ctx) throws SQLE | |
| } | ||
| ); | ||
|
|
||
| if (segments == null || segments.isEmpty()) { | ||
| log.info("No segments found in the database!"); | ||
| if (segments == null) { | ||
| log.wtf("Observed 'null' when polling segments from the db, aborting snapshot update."); | ||
| return; | ||
| } | ||
|
|
||
| log.info("Polled and found %,d segments in the database", segments.size()); | ||
|
|
||
| ImmutableMap<String, String> dataSourceProperties = createDefaultDataSourceProperties(); | ||
|
|
||
| // dataSourcesSnapshot is updated only here and the DataSourcesSnapshot object is immutable. If data sources or | ||
| // segments are marked as used or unused directly (via markAs...() methods in MetadataSegmentManager), the | ||
| // dataSourcesSnapshot can become invalid until the next database poll. | ||
|
|
@@ -967,6 +963,13 @@ public DataSegment map(int index, ResultSet r, StatementContext ctx) throws SQLE | |
| // segment mark calls in rapid succession. So the snapshot update is not done outside of database poll at this time. | ||
| // Updates outside of database polls were primarily for the user experience, so users would immediately see the | ||
| // effect of a segment mark call reflected in MetadataResource API calls. | ||
|
|
||
| ImmutableMap<String, String> dataSourceProperties = createDefaultDataSourceProperties(); | ||
| if (segments.isEmpty()) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This part is the fix, right? (Continuing on even if It looks good to me. |
||
| log.info("No segments found in the database!"); | ||
| } else { | ||
| log.info("Polled and found %,d segments in the database", segments.size()); | ||
| } | ||
| dataSourcesSnapshot = DataSourcesSnapshot.fromUsedSegments( | ||
| Iterables.filter(segments, Objects::nonNull), // Filter corrupted entries (see above in this method). | ||
| dataSourceProperties | ||
|
|
||
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.
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.
This code is pointless, since
.list()above cannot return null andinReadOnlyTransactionwill not convert a nonnull return to null. Might as well remove it, or include aPreconditions.checkNotNullor something (throw an exception on the unanticipatednullrather than returning early and leaving thesnapshotnull).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.
Preconditionscheck makes sense to me, to control the error messaging here instead of allowing the NPE to happen downstream, will updateThere 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.
Er, actually this is just in the poll, i guess the NPE would still potentially happen, regardless that approach seems cleaner.