You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Thomas Draier (JIRA)" <ji...@apache.org> on 2016/04/08 11:26:25 UTC

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

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

Thomas Draier resolved UNOMI-22.
--------------------------------
    Resolution: Fixed

> 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
>
> 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)