[CAMEL-13606] Olingo Consumer filtering can cause NPE

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.21.5
• Fix Version/s: 2.24.1, 3.0.0.M4, 3.0.0, 2.25.0
• Component/s: camel-olingo2, camel-olingo4
• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: Paul Richardson
• Created: 03/Jun/19 12:20
• Updated: 06/Jun/19 07:19
• Resolved: 06/Jun/19 07:19

Description

When polling with the Olingo*Consumer, the result is intercepted and filtered (if filtering is switched on). If a key predicate is used as well then, on subsequent polling iterations, the result is filtered to return null. When the result is then intercepted and passed to the Olingo*Index for indexing, the latter fails to handle the null value and causes an NullPointerException. This exception is reported/logged and polling continues with subsequent iterations (also blowing up with NPEs). Need to fix the Index classes so they handle null values correctly.