[ML] Avoid NPE in maybeStartAllocation in AdaptiveAllocations #114958
Conversation
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
maxhniebergall
added
>bug
:ml
maxhniebergall
requested review from
davidkyle and
jan-elastic
and removed request for
jan-elastic
|
Pinging @elastic/ml-core (Team:ML) |
|
Hi @maxhniebergall, I've created a changelog YAML for you. |
|
closed as duplicate of https://github.com/elastic/elasticsearch/pull/114880/files |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@wwang500 reported an NPE from this line, which seems to be due to auto-unboxing of the null value stored in getMinNumberOfAllocations. With this change, we will use the equals method of a cached Integer object which cannot be null.
Non-issue as this was caught in QA