SAMOA-73: fixes NullPointerException in VerticalHoeffdingTree #73
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.
java.lang.NullPointerException is in some cases thrown in org.apache.samoa.learners.classifiers.trees.ModelAggregatorProcessor.process(ModelAggregatorProcessor.java:142)
The problem occurs because FoundNode objects in some cases contain null node property. Such FoundNode objects can be created and are considered valid, which directly follows from filterInstanceToLeaf(Instance inst, SplitNode parent, int parentBranch) method of SplitNode class.
However, once a categorical feature is selected for the splits, the following situation can happen:
Solution: In such cases, the FoundNode object should reflect the newly created tree extension. This can be done by injecting into the FoundNode the newly created Node object. This is to keep FoundNode in sync with the most recent tree structure. This is what this fix makes: it replaces null node object with the newly created one.