[
https://issues.apache.org/jira/browse/UNOMI-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Draier updated UNOMI-22:
-------------------------------
Fix Version/s: 1.1.0-incubating
> Filters with "or" condition between session/user conditions do not work
> -----------------------------------------------------------------------
>
> Key: UNOMI-22
> URL: https://issues.apache.org/jira/browse/UNOMI-22
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Thomas Draier
> Assignee: Thomas Draier
> Fix For: 1.1.0-incubating
>
>
> 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".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
