ProtobufMatcherEvalContext should also fire missing properties -------------------------------------------------------------- Key: ISPN-4319 URL: https://issues.jboss.org/browse/ISPN-4319 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 7.0.0.Alpha4 Reporter: Adrian Nistor Assignee: Adrian Nistor Labels: 630 Fix For: 7.0.0.Beta1 Not doing so leads to 'is null' predicates not being evaluated precisely because the property is null, which leads to an incorrect match result. This issue does not happen in the reflection based case. Missing properties should be fired with their default value if they have one, otherwise with null, unless their type is not nullable in which case nothing needs to be done for them.