[UNOMI-22] Filters with "or" condition between session/user conditions do not work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: unomi-1.1.0-incubating
• Assignee: Thomas Draier
• Reporter: Thomas Draier
• Created: 08/Apr/16 09:17
• Updated: 20/Sep/16 08:07
• Resolved: 08/Apr/16 09:25

Description

When passing the following condition in a filter :

{
"type": "booleanCondition",
"parameterValues": {
"operator": "or",
"subConditions": [
{
"type": "profilePropertyCondition",
"parameterValues":

{ "propertyName": "properties.firstName", "comparisonOperator": "equals", "propertyValue": "ffds" }

},
{
"type": "geoLocationSessionCondition",
"parameterValues":

{ "country": "AI" }

}
]
}
}

We receive an IllegalArgumentException . Any "or" condition between a session and profile condition will throw an exception. It should be possible to evaluate the condition on the current session, even the condition types are mixed.
Note that it works if the operator is "and".