You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2018/05/06 19:21:00 UTC
[jira] [Commented] (UNOMI-97) Conditions Spanning Multiple Types
[ https://issues.apache.org/jira/browse/UNOMI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465263#comment-16465263 ]
Serge Huber commented on UNOMI-97:
----------------------------------
This issue is a bit dated now, is this still an open issue ?
> Conditions Spanning Multiple Types
> ----------------------------------
>
> Key: UNOMI-97
> URL: https://issues.apache.org/jira/browse/UNOMI-97
> Project: Apache Unomi
> Issue Type: Test
> Components: core
> Affects Versions: 1.2.0-incubating, 1.3.0-incubating
> Reporter: Damon Henry
> Priority: Minor
> Fix For: 1.4.0-incubating
>
>
> I'm attempting to create boolean conditions that retrieve unique profile counts but I may be interpreting the documentation incorrectly. A contrived example is asking the context server to give me all profiles performing a page view event. The example below provides the expected result when querying the *event* type but return 0 when querying the *profile* type.
> Is there a method to build segments using attributes from profiles, sessions, and events?
> http://localhost/cxs/query/event/count (return expected correct number of events)
> http://localhost/cxs/query/profile/count (returns zero; should this return unique profiles)
> {code}
> {
> "parameterValues": {
> "operator": "and",
> "subConditions": [
> {
> "parameterValues": {
> "propertyValue": "page",
> "comparisonOperator": "equals",
> "propertyName": "target.itemType"
> },
> "type": "eventPropertyCondition"
> },
> {
> "parameterValues": {
> "propertyValue": "view",
> "comparisonOperator": "equals",
> "propertyName": "eventType"
> },
> "type": "eventPropertyCondition"
> }
> ]
> },
> "type": "booleanCondition"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)