Potential null pointer exception [LUCENE-6626]
Open
affects-version:6.0
legacy-jira-fix-version:6.0
legacy-jira-label:github-pullrequest
legacy-jira-priority:Minor
module:queryparser
type:bug
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
In the file `ModifierQueryNode.java`, `getChild()` and `getChildren` could return null. Checks need to be made for the same to avoid null pointer exceptions.
---
Migrated from [LUCENE-6626](https://issues.apache.org/jira/browse/LUCENE-6626) by Rishabh Patel, updated May 09 2016
Contributor guide
Research direction
Start in ModifierQueryNode.java by inspecting getChild() and getChildren() and how their results are used. Add the needed null handling so these methods cannot lead to null pointer exceptions, then verify that the affected query-node behavior remains correct with the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100