[
https://issues.apache.org/jira/browse/UNOMI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168032#comment-16168032
]
Don Hinshaw commented on UNOMI-97:
----------------------------------
Serge,
Thanks for your help. If you don't mind me asking, how do you handle this use
case?
Do you see value in querying profiles based on both session and event
information?
If we decide to pursue this enhancement, it seems to me like there is more
value in adding a condition for sessionProperties that can be used with a
profileCondition.
Any thoughts?
Thanks,
Don
> 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
> Reporter: Damon Henry
> Priority: Minor
> Fix For: 1.3.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
(v6.4.14#64029)
