fix(browseDAO): Handle null browse path from ES in BrowseDAO #11875
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.
Checklist
Background:
In PR: https://github.com/datahub-project/datahub/pull/11514/files, empty strings were considered as null for ES indexing.
In Kibana:
From DB (aspect):
Issue:
This is causing null pointer exception for entities, where browse path is empty string.
Which is emulated in the below test:
Have added test for the changes as well.