-
Notifications
You must be signed in to change notification settings - Fork 219
Primary to Secondary Mapper #1300
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
Conversation
primaryToSecondaryIndex = | ||
new PrimaryToSecondaryIndex<>(configuration.getSecondaryToPrimaryMapper()); | ||
} else { | ||
primaryToSecondaryIndex = null; |
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.
Maybe it'd be cleaner to have a no-op index instead of setting it to null
and having to guard for null
everywhere else?
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.
Not sure about that, it is very explicit this way, that the index is not used in that case.
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.
But also fine with that. Will try how that looks.
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.
One doesn't prevent the other: we could have a NOOP index and still be able to make it explicit when needed (i.e. useSecondaryToPrimaryIndex
could check if the set index is the NOOP one instead of null
where we need to know for sure whether to use it or not). Not a showstopper in any case.
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.
Changed.
Attila, thank you very much for the prompt fix, I have tested this PR locally. I can confirm this addresses the issue we hit in FLINK-28008. Do you already have an ETA for the 3.0.3 patch release? |
@morhidi thx for feedback, glad to hear, after this issue is merged we can release v3.0.3, hopefully today or Monday. |
Kudos, SonarCloud Quality Gate passed! |
see related issue