Add error handling for jsonPathString UDF when jsonPath is non-existent
Open
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
If you use "non default value" version i.e **jsonPathString(Object object, String jsonPath)** then there is no error handling in case jsonPath doesn't exist and will cause data ingestion to fail. Need to return null in such scenarios so data ingestion is not impacted.
Similar to above function other functions for e.g jsonPathDouble() etc. need to be updated as well.
cc @npawar
Contributor guide
Research direction
Start by locating the jsonPathString(Object object, String jsonPath) UDF and the related jsonPathDouble() and other jsonPath functions. Check how they handle a non-existent jsonPath, then verify that each affected function returns null so ingestion is not interrupted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100