I think I've reported something similar already:
https://issues.apache.org/jira/browse/CAY-1877
Perhaps this can be updated with additional details.
Dima
On 02/22/2014 12:50 PM, Andrus Adamchik wrote:
Sounds like a bug. Could you open a Jira please?
Thanks,
Andrus
On Feb 22, 2014, at 1:33 AM, David Feshbach <[email protected]> wrote:
I came across a breaking change in the way expressions are evaluated in memory
when trying out trunk. A null value on the left hand side of a comparison
(ASTGreater in my case) used to cause evaluateNode to return false. Now it
throws an UnsupportedOperationException. A null value on the right hand side of
a comparison used to return false, now it throws a NullPointerException. I'm
not sure how I would get around this without littering all my expressions with
isNotNulls. Maybe Expression.match could catch the exceptions and return false?
