[Backport 2.0] handling null pointer exception in multi-filed mapping #787
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.
Description
Backport 501bd28 from #757
When replication started from leader index to follower followe index with empty data (empty mapping). It throws null pointer exception in multi-field mapping. This issue as such don't create any pause but mapping source, mapping properties variables are not nullable earlier were made nullable to stop throwing these errors.
Issues Resolved
nullPointerException while calling leader mapping source.
#622