[
https://issues.apache.org/jira/browse/UNOMI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163445#comment-16163445
]
Don Hinshaw edited comment on UNOMI-97 at 9/12/17 6:44 PM:
-----------------------------------------------------------
[~shuber] We are able to get the profile count based on events with
pastEventsCondition. The problem is joining that query with the session data
(view event and android device for example).
If we had a rule that could set event properties with values from our sessions
we could used pastEventCondition to get what we need. It seems to me that the
setPropertyAction only sets properties for either the profile or the session
(not events). See line 75 in SetPropertyAction.java.
Does it makes sense to you to add an action that can set properties on the
event from the session, or modify the existing setPropertyAction to support
events?
If we did that we could add the session properties we are interested in to our
event and get profile counts that way.
was (Author: donald_kortx):
[~shuber] We are able to get the profile count based on events with
pastEventsCondition. The problem is joining that query with the session data
(view event and android device for example).
If we had a rule that could set event properties with values from our sessions
we could used pastEventCondition to get what we need. It seems to me that the
setPropertyAction only sets properties for either the profile or the session
(not events). See line 75 in SetPropertyAction.java.
Does it makes sense to you to add an action that can set properties on the
event from the session?
If we did that we could add the session properties we are interested in to our
event and get profile counts that way.
> 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)
