[ 
https://issues.apache.org/jira/browse/CAMEL-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-13606:
--------------------------------
    Fix Version/s: 3.0.0.M4
                   2.25.0
                   2.24.1
                   2.23.3
                   3.0.0

> Olingo Consumer filtering can cause NPE
> ---------------------------------------
>
>                 Key: CAMEL-13606
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13606
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-olingo2, camel-olingo4
>    Affects Versions: 2.21.5
>            Reporter: Paul Richardson
>            Priority: Major
>             Fix For: 3.0.0, 2.23.3, 2.24.1, 2.25.0, 3.0.0.M4
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to