[jira] [Resolved] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwang-in (Dennis) JUNG resolved UNOMI-80. - Resolution: Fixed > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Attachments: karaf.log > > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870941#comment-15870941 ] Kwang-in (Dennis) JUNG commented on UNOMI-80: - [~bhillou] Thanks for help! I'll close this issue. > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Attachments: karaf.log > > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwang-in (Dennis) JUNG closed UNOMI-80. --- Resolution: Fixed > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Attachments: karaf.log > > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwang-in (Dennis) JUNG reopened UNOMI-80: - > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Attachments: karaf.log > > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-82) Same profileId associated with different sessions (different users)
Damon Henry created UNOMI-82: Summary: Same profileId associated with different sessions (different users) Key: UNOMI-82 URL: https://issues.apache.org/jira/browse/UNOMI-82 Project: Apache Unomi Issue Type: Bug Components: core Affects Versions: 1.2.0-incubating Environment: Ubuntu 14.04, ES 5.2 cluster, two EC2 instances behind an ELB Reporter: Damon Henry Fix For: 1.2.0-incubating During testing we've noticed, in some instances, the same profileId is associated with large numbers of sessions when calling the /profiles/search/sessions endpoint as if the profileId is being cached. The sessionCity (and other geo attributes) indicate the sessions are originating from unrelated locations making it unlikely the sessions belong the same user (e.g. profileId). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-85) REST API & JavaDoc documentation page return 404
[ https://issues.apache.org/jira/browse/UNOMI-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876898#comment-15876898 ] Romain Blineau commented on UNOMI-85: - Thank you ! > REST API & JavaDoc documentation page return 404 > > > Key: UNOMI-85 > URL: https://issues.apache.org/jira/browse/UNOMI-85 > Project: Apache Unomi > Issue Type: Bug > Components: website >Affects Versions: 1.0.0-incubating >Reporter: Romain Blineau >Assignee: Serge Huber > Fix For: 1.2.0-incubating > > > Accessing REST API documentation returns a 404 response. > 2 ways to reproduce: > * From http://unomi.incubator.apache.org/ click in menu "documentation" and > then "REST API documentation" & "Java Doc" > * Directly access URL > http://unomi.incubator.apache.org/rest-api-doc/index.html or > http://unomi.incubator.apache.org/unomi-api/apidocs/index.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (UNOMI-79) Create end point to allow the creation of personas with sessions
[ https://issues.apache.org/jira/browse/UNOMI-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD reassigned UNOMI-79: Assignee: Damien GAILLARD > Create end point to allow the creation of personas with sessions > > > Key: UNOMI-79 > URL: https://issues.apache.org/jira/browse/UNOMI-79 > Project: Apache Unomi > Issue Type: Improvement >Affects Versions: 1.2.0-incubating >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-79) Create end point to allow the creation of personas with sessions
Damien GAILLARD created UNOMI-79: Summary: Create end point to allow the creation of personas with sessions Key: UNOMI-79 URL: https://issues.apache.org/jira/browse/UNOMI-79 Project: Apache Unomi Issue Type: Improvement Affects Versions: 1.2.0-incubating Reporter: Damien GAILLARD Fix For: 1.2.0-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-80) Stopped in initializing
Kwang-in (Dennis) JUNG created UNOMI-80: --- Summary: Stopped in initializing Key: UNOMI-80 URL: https://issues.apache.org/jira/browse/UNOMI-80 Project: Apache Unomi Issue Type: Test Reporter: Kwang-in (Dennis) JUNG Priority: Trivial Hello~just joined! I'm following up instruction guide, but it stops while init when starting with 'karaf start'. ``` karaf@root()> Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" java.lang.RuntimeException: Port already in use: 4; You may have started two containers. If you need to start a second container or the default ports are already in use update the config file etc/org.apache.karaf.management.cfg and change the Registry Port and Server Port to unused ports at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) Initializing Unomi... ``` It does not go on as mentioned in getting started page. http://unomi.incubator.apache.org/getting-started.html Also, I've failed in integration test(others are all success). Is it related with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867764#comment-15867764 ] Serge Huber commented on UNOMI-80: -- Hello, Thanks for testing. At this time the integration and performance tests are not working so we deactivated them by default For the other you probably already have something running on the port 4. If you launched the integration test, it is very likely that you have a Java process still running with Karaf, this is a known problem. Make sure you kill any residual processes before launching Karaf. Best regards, Serge... > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-80) Stopped in initializing
[ https://issues.apache.org/jira/browse/UNOMI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870241#comment-15870241 ] Serge Huber commented on UNOMI-80: -- Yes to use the Twitter example you will need a Twitter developer account and an API Key. Currently there are no plans for SNS due to limited resources, we are hoping we can encourage contributors to help us with integrations. Best regards, Serge... > Stopped in initializing > --- > > Key: UNOMI-80 > URL: https://issues.apache.org/jira/browse/UNOMI-80 > Project: Apache Unomi > Issue Type: Test >Reporter: Kwang-in (Dennis) JUNG >Priority: Trivial > Attachments: karaf.log > > > Hello~just joined! > I'm following up instruction guide, but it stops while init when starting > with 'karaf start'. > ``` > karaf@root()> Exception in thread "JMX Connector Thread > [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]" > java.lang.RuntimeException: > Port already in use: 4; > You may have started two containers. If you need to start a second container > or the default ports are already in use update the config file > etc/org.apache.karaf.management.cfg and change the Registry Port and Server > Port to unused ports > at > org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:278) > Initializing Unomi... > ``` > It does not go on as mentioned in getting started page. > http://unomi.incubator.apache.org/getting-started.html > Also, I've failed in integration test(others are all success). Is it related > with this? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (UNOMI-21) Make the default location configurable instead of hardcoded.
[
https://issues.apache.org/jira/browse/UNOMI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber resolved UNOMI-21.
--
Resolution: Fixed
Settings have been moved to configuration file :
org.apache.unomi.plugins.request.cfg
And the configuration documentation has been updated to document these settings.
> Make the default location configurable instead of hardcoded.
>
>
> Key: UNOMI-21
> URL: https://issues.apache.org/jira/browse/UNOMI-21
> Project: Apache Unomi
> Issue Type: Improvement
> Components: core
>Affects Versions: 1.0.0-incubating, 1.1.0-incubating
>Reporter: Serge Huber
>Priority: Minor
> Fix For: 1.2.0-incubating
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently in the file
> /Users/loom/java/technologies/apache-git/incubator-unomi/plugins/request/src/main/java/org/apache/unomi/plugins/request/actions/SetRemoteHostInfoAction.java
> We have the following hardcoded location :
> {code}
> session.setProperty("sessionCountryCode", "CH");
> session.setProperty("sessionCountryName", "Switzerland");
> session.setProperty("sessionCity", "Geneva");
> session.setProperty("sessionAdminSubDiv1", "GE");
> session.setProperty("sessionAdminSubDiv2", "2500");
> session.setProperty("sessionIsp", "Cablecom");
> Map<String, Double> location = new HashMap<String, Double>();
> location.put("lat", 46.1884341);
> location.put("lon", 6.1282508);
> session.setProperty("location", location);
> {code}
> We should make this configurable using OSGi configuration
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (UNOMI-77) Add inContains Comparison Operator
[ https://issues.apache.org/jira/browse/UNOMI-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-77. Resolution: Fixed > Add inContains Comparison Operator > -- > > Key: UNOMI-77 > URL: https://issues.apache.org/jira/browse/UNOMI-77 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani >Priority: Minor > Fix For: 1.2.0-incubating > > > Add InContains Comparison Operator: test if the profile property contains > (String) at least one of values provided in the condition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-73) Add a log when Unomi is properly initialized.
Serge Huber created UNOMI-73: Summary: Add a log when Unomi is properly initialized. Key: UNOMI-73 URL: https://issues.apache.org/jira/browse/UNOMI-73 Project: Apache Unomi Issue Type: Bug Components: core Affects Versions: 1.1.0-incubating, 1.0.0-incubating Reporter: Serge Huber Assignee: Serge Huber Fix For: 1.2.0-incubating Currently there is no log message or notification that tells an Apache Unomi administrator when the system has properly started up. Having a global lifecycle listener that would check for service registration and make sure that all required services are properly setup and that all expected bundles are started and then display a message in the logs and in the System.out console would be a great help. This system could also in the future track bundle startup time to help optimize startup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-74) Improve user agent reporting to handle browser like Edge
Damien GAILLARD created UNOMI-74: Summary: Improve user agent reporting to handle browser like Edge Key: UNOMI-74 URL: https://issues.apache.org/jira/browse/UNOMI-74 Project: Apache Unomi Issue Type: Bug Affects Versions: 1.2.0-incubating Reporter: Damien GAILLARD Assignee: Damien GAILLARD Fix For: 1.2.0-incubating more informations here: http://stackoverflow.com/questions/31870789/check-whether-browser-is-chrome-or-edge so as today after doing some test if you display a page with: - IE on Xbox One = Chrome - Edge on smartphone = Safari - Edge on computer = Chrome - IE11 on computer = Mozilla 11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-74) Improve user agent reporting to handle browser like Edge
[ https://issues.apache.org/jira/browse/UNOMI-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832095#comment-15832095 ] Damien GAILLARD commented on UNOMI-74: -- We are using https://github.com/before/uadetector to detect browser but this library didn't evolve since 2014 no release and no commit on the repo > Improve user agent reporting to handle browser like Edge > > > Key: UNOMI-74 > URL: https://issues.apache.org/jira/browse/UNOMI-74 > Project: Apache Unomi > Issue Type: Bug >Affects Versions: 1.2.0-incubating >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.2.0-incubating > > > more informations here: > http://stackoverflow.com/questions/31870789/check-whether-browser-is-chrome-or-edge > so as today after doing some test if you display a page with: > - IE on Xbox One = Chrome > - Edge on smartphone = Safari > - Edge on computer = Chrome > - IE11 on computer = Mozilla 11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-73) Add a log when Unomi is properly initialized.
[ https://issues.apache.org/jira/browse/UNOMI-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber resolved UNOMI-73. -- Resolution: Fixed > Add a log when Unomi is properly initialized. > - > > Key: UNOMI-73 > URL: https://issues.apache.org/jira/browse/UNOMI-73 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.0.0-incubating, 1.1.0-incubating >Reporter: Serge Huber >Assignee: Serge Huber > Fix For: 1.2.0-incubating > > > Currently there is no log message or notification that tells an Apache Unomi > administrator when the system has properly started up. > Having a global lifecycle listener that would check for service registration > and make sure that all required services are properly setup and that all > expected bundles are started and then display a message in the logs and in > the System.out console would be a great help. > This system could also in the future track bundle startup time to help > optimize startup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (UNOMI-33) Profile CSV export should contain custom properties as well (e.g. set by form mapping)
[ https://issues.apache.org/jira/browse/UNOMI-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand reassigned UNOMI-33: - Assignee: Quentin Lamerand > Profile CSV export should contain custom properties as well (e.g. set by form > mapping) > -- > > Key: UNOMI-33 > URL: https://issues.apache.org/jira/browse/UNOMI-33 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-82) Same profileId associated with different sessions (different users)
[ https://issues.apache.org/jira/browse/UNOMI-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885502#comment-15885502 ] Damon Henry commented on UNOMI-82: -- I resolved the issue but would like to confirm that I'm using the sessions properly. I have generateUUID JavaScript method that creates a unique id for every event. You stated the sessions should be similar to server-side sessions. Does this mean the same session id should be persisted and used for all events occurring for a session's duration? > Same profileId associated with different sessions (different users) > --- > > Key: UNOMI-82 > URL: https://issues.apache.org/jira/browse/UNOMI-82 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.2.0-incubating > Environment: Ubuntu 14.04, ES 5.2 cluster, two EC2 instances behind > an ELB >Reporter: Damon Henry > Fix For: 1.2.0-incubating > > > During testing we've noticed, in some instances, the same profileId is > associated with large numbers of sessions when calling the > /profiles/search/sessions endpoint as if the profileId is being cached. The > sessionCity (and other geo attributes) indicate the sessions are originating > from unrelated locations making it unlikely the sessions belong the same user > (e.g. profileId). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-57) Fix LGPL license issues within binary build
Thomas Draier created UNOMI-57: -- Summary: Fix LGPL license issues within binary build Key: UNOMI-57 URL: https://issues.apache.org/jira/browse/UNOMI-57 Project: Apache Unomi Issue Type: Bug Reporter: Thomas Draier Assignee: Thomas Draier -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-58) issue when deploying binary package
Thomas Draier created UNOMI-58: -- Summary: issue when deploying binary package Key: UNOMI-58 URL: https://issues.apache.org/jira/browse/UNOMI-58 Project: Apache Unomi Issue Type: Bug Reporter: Thomas Draier Assignee: Thomas Draier The copy-karaf target crashes when deploying jars to repository, because it actually tries to move the same file twice. Using a copy instead would avoid the issue -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-58) issue when deploying binary package
[ https://issues.apache.org/jira/browse/UNOMI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier resolved UNOMI-58. Resolution: Fixed > issue when deploying binary package > --- > > Key: UNOMI-58 > URL: https://issues.apache.org/jira/browse/UNOMI-58 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > The copy-karaf target crashes when deploying jars to repository, because it > actually tries to move the same file twice. Using a copy instead would avoid > the issue -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-58) issue when deploying binary package
[ https://issues.apache.org/jira/browse/UNOMI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-58: --- Fix Version/s: 1.1.0-incubating > issue when deploying binary package > --- > > Key: UNOMI-58 > URL: https://issues.apache.org/jira/browse/UNOMI-58 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > The copy-karaf target crashes when deploying jars to repository, because it > actually tries to move the same file twice. Using a copy instead would avoid > the issue -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-57) Fix LGPL license issues within binary build
[ https://issues.apache.org/jira/browse/UNOMI-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier resolved UNOMI-57. Resolution: Fixed > Fix LGPL license issues within binary build > --- > > Key: UNOMI-57 > URL: https://issues.apache.org/jira/browse/UNOMI-57 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-58) issue when deploying binary package
[ https://issues.apache.org/jira/browse/UNOMI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier closed UNOMI-58. -- > issue when deploying binary package > --- > > Key: UNOMI-58 > URL: https://issues.apache.org/jira/browse/UNOMI-58 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > The copy-karaf target crashes when deploying jars to repository, because it > actually tries to move the same file twice. Using a copy instead would avoid > the issue -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-56) Add setPropertyValueMultiple in setPropertyAction.json
Abdelkader Midani created UNOMI-56: -- Summary: Add setPropertyValueMultiple in setPropertyAction.json Key: UNOMI-56 URL: https://issues.apache.org/jira/browse/UNOMI-56 Project: Apache Unomi Issue Type: Bug Components: core Reporter: Abdelkader Midani -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-23) Allows to dynamically add custom conditions
[ https://issues.apache.org/jira/browse/UNOMI-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier closed UNOMI-23. -- > Allows to dynamically add custom conditions > --- > > Key: UNOMI-23 > URL: https://issues.apache.org/jira/browse/UNOMI-23 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > I was thinking of some possible improvements on the condition types, to make > them more flexible. > Currently, condition types are defined in unomi plugins - they are read from > a json inside a plugin bundle, and then loaded into memory. Some of the base > conditions rely on actual java code, so it make sense to put them into a > bundle - but other some other conditions are only simple combination of other > conditions, and are usually very specific to a domain. An end user may want > to create his own condition using simple JSON definition, and may not want to > develop and deploy a bundle just for that. It would be nice to be able to add > new condition types by simply using REST API. > If you look at the pageViewEventCondition - it is only based on simple > boolean and property conditions, and is very specific to the type of events > that will be sent by a third party server. They should get out of default > unomi installation, and rather be created directly by the server that will > send these events. > Allowing to create/edit conditions will of course require to persist them, > and so require some changes in the ConditionType object, changing from > "PluginType" to "Item", and the way they are read by the definitions service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-20) birthDate range definition is inconsistent
[ https://issues.apache.org/jira/browse/UNOMI-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-20: --- Fix Version/s: 1.1.0-incubating > birthDate range definition is inconsistent > -- > > Key: UNOMI-20 > URL: https://issues.apache.org/jira/browse/UNOMI-20 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier >Priority: Minor > Fix For: 1.1.0-incubating > > > The birthDate property defines inconsistent ranges : they not get all > possible values (ranges from now to now-10y, next range start at now-11y) and > has overlaps (one range is 10 years ago to now, another range is 51 years ago > to now) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-23) Allows to dynamically add custom conditions
[ https://issues.apache.org/jira/browse/UNOMI-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-23: --- Fix Version/s: 1.1.0-incubating > Allows to dynamically add custom conditions > --- > > Key: UNOMI-23 > URL: https://issues.apache.org/jira/browse/UNOMI-23 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > I was thinking of some possible improvements on the condition types, to make > them more flexible. > Currently, condition types are defined in unomi plugins - they are read from > a json inside a plugin bundle, and then loaded into memory. Some of the base > conditions rely on actual java code, so it make sense to put them into a > bundle - but other some other conditions are only simple combination of other > conditions, and are usually very specific to a domain. An end user may want > to create his own condition using simple JSON definition, and may not want to > develop and deploy a bundle just for that. It would be nice to be able to add > new condition types by simply using REST API. > If you look at the pageViewEventCondition - it is only based on simple > boolean and property conditions, and is very specific to the type of events > that will be sent by a third party server. They should get out of default > unomi installation, and rather be created directly by the server that will > send these events. > Allowing to create/edit conditions will of course require to persist them, > and so require some changes in the ConditionType object, changing from > "PluginType" to "Item", and the way they are read by the definitions service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-25) CSV export do not contains user segments
[ https://issues.apache.org/jira/browse/UNOMI-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier closed UNOMI-25. -- > CSV export do not contains user segments > > > Key: UNOMI-25 > URL: https://issues.apache.org/jira/browse/UNOMI-25 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > It would be nice to include segment names in CSV profile export -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-29) Event chain can be executed on previous profile in case of profile switch
[ https://issues.apache.org/jira/browse/UNOMI-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-29: --- Fix Version/s: 1.1.0-incubating > Event chain can be executed on previous profile in case of profile switch > - > > Key: UNOMI-29 > URL: https://issues.apache.org/jira/browse/UNOMI-29 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > When the MergeProfiles action is executed and detect a profile switch (user > is logging out / logging in with a different user), the rest of the actions, > like EvaluateProfileSegmentsAction, are executed on the previous profile, > where they should be called on the new profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-25) CSV export do not contains user segments
[ https://issues.apache.org/jira/browse/UNOMI-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-25: --- Fix Version/s: 1.1.0-incubating > CSV export do not contains user segments > > > Key: UNOMI-25 > URL: https://issues.apache.org/jira/browse/UNOMI-25 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > It would be nice to include segment names in CSV profile export -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-55) typing issue in defaultDeniedProperties (org.apache.unomi.privacy.cfg)
[ https://issues.apache.org/jira/browse/UNOMI-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-55: --- Fix Version/s: 1.1.0-incubating > typing issue in defaultDeniedProperties (org.apache.unomi.privacy.cfg) > -- > > Key: UNOMI-55 > URL: https://issues.apache.org/jira/browse/UNOMI-55 > Project: Apache Unomi > Issue Type: Bug >Reporter: Damien GAILLARD > Fix For: 1.1.0-incubating > > > Tested CXS 1.1.0 #685: > - open /etc/org.apache.unomi.privacy.cfg > - the property "linedInId" has a typing issue - the "k" is missing > -> please add (linkedInId) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-54) Add mappings for scoring and userList + add score mapping in profile
[ https://issues.apache.org/jira/browse/UNOMI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-54: --- Fix Version/s: 1.1.0-incubating > Add mappings for scoring and userList + add score mapping in profile > > > Key: UNOMI-54 > URL: https://issues.apache.org/jira/browse/UNOMI-54 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-48) Add validation to scoring plan deletion
[ https://issues.apache.org/jira/browse/UNOMI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-48: --- Fix Version/s: 1.1.0-incubating > Add validation to scoring plan deletion > --- > > Key: UNOMI-48 > URL: https://issues.apache.org/jira/browse/UNOMI-48 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > > Like for the segments, add validation to scoring plan deletion to check > before if it's used elsewhere in a condition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-46) Avoid NPE when asking for the definition of a missing tag + Return 404
[ https://issues.apache.org/jira/browse/UNOMI-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-46: --- Fix Version/s: 1.1.0-incubating > Avoid NPE when asking for the definition of a missing tag + Return 404 > -- > > Key: UNOMI-46 > URL: https://issues.apache.org/jira/browse/UNOMI-46 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-26) Query default limit is 0 (no results)
[ https://issues.apache.org/jira/browse/UNOMI-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier closed UNOMI-26. -- > Query default limit is 0 (no results) > - > > Key: UNOMI-26 > URL: https://issues.apache.org/jira/browse/UNOMI-26 > Project: Apache Unomi > Issue Type: Bug >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > When using a Query object through the rest endpoint, default limit is 0, so > no results are returned . We should either use -1 or a higher default value > for the result size limit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (UNOMI-30) Move out specific conditions/rules from unomi
[ https://issues.apache.org/jira/browse/UNOMI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier reopened UNOMI-30: > Move out specific conditions/rules from unomi > - > > Key: UNOMI-30 > URL: https://issues.apache.org/jira/browse/UNOMI-30 > Project: Apache Unomi > Issue Type: Task >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > Lot of conditions provided by default in Unomi are actually related to Jahia > usage and should be moved out from the standard package. It now possible to > dynamically register custom condition/rules thanks to UNOMI-23 . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-30) Move out specific conditions/rules from unomi
[ https://issues.apache.org/jira/browse/UNOMI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier closed UNOMI-30. -- Resolution: Fixed > Move out specific conditions/rules from unomi > - > > Key: UNOMI-30 > URL: https://issues.apache.org/jira/browse/UNOMI-30 > Project: Apache Unomi > Issue Type: Task >Reporter: Thomas Draier >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > > Lot of conditions provided by default in Unomi are actually related to Jahia > usage and should be moved out from the standard package. It now possible to > dynamically register custom condition/rules thanks to UNOMI-23 . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-43) Improve logging in context and event servlets
[ https://issues.apache.org/jira/browse/UNOMI-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber closed UNOMI-43. > Improve logging in context and event servlets > - > > Key: UNOMI-43 > URL: https://issues.apache.org/jira/browse/UNOMI-43 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Affects Versions: 1.0.0-incubating, 1.1.0-incubating >Reporter: Serge Huber >Assignee: Serge Huber > Fix For: 1.1.0-incubating > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Currently in both the context servlet and event collector servlets when some > conditions are not met we simply stop the request processing without even any > server-side logs. > We should improve this so that we can provide logs to analyze any potential > problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-42) Fix version numbers in build scripts
[ https://issues.apache.org/jira/browse/UNOMI-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber closed UNOMI-42. > Fix version numbers in build scripts > > > Key: UNOMI-42 > URL: https://issues.apache.org/jira/browse/UNOMI-42 > Project: Apache Unomi > Issue Type: Improvement > Components: build, core >Affects Versions: 1.1.0-incubating >Reporter: Serge Huber >Assignee: Serge Huber > Labels: easyfix > Fix For: 1.1.0-incubating > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > We currently have not updated the build scripts to use the new versions. > Instead of this we should put the version numbers in a setenv file or even > better find a way to update them dynamically from the pom.xml file (if > possible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-12) Unomi sample plugin should specify target and tags for created properties
[ https://issues.apache.org/jira/browse/UNOMI-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Laprun closed UNOMI-12. -- > Unomi sample plugin should specify target and tags for created properties > - > > Key: UNOMI-12 > URL: https://issues.apache.org/jira/browse/UNOMI-12 > Project: Apache Unomi > Issue Type: Bug >Reporter: Christophe Laprun >Priority: Minor > Fix For: 1.0.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-6) Move example code to Unomi codebase.
[ https://issues.apache.org/jira/browse/UNOMI-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Laprun closed UNOMI-6. - > Move example code to Unomi codebase. > > > Key: UNOMI-6 > URL: https://issues.apache.org/jira/browse/UNOMI-6 > Project: Apache Unomi > Issue Type: New Feature >Reporter: Christophe Laprun >Priority: Minor > Fix For: 1.0.0-incubating > > > The code currently sits at: > https://github.com/metacosm/unomi-tweet-button-plugin and > https://github.com/metacosm/unomi-tweet-button -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-47) Add possibility to limit to one notification mail
[ https://issues.apache.org/jira/browse/UNOMI-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-47. - > Add possibility to limit to one notification mail > - > > Key: UNOMI-47 > URL: https://issues.apache.org/jira/browse/UNOMI-47 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-48) Add validation to scoring plan deletion
[ https://issues.apache.org/jira/browse/UNOMI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-48. - > Add validation to scoring plan deletion > --- > > Key: UNOMI-48 > URL: https://issues.apache.org/jira/browse/UNOMI-48 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > > Like for the segments, add validation to scoring plan deletion to check > before if it's used elsewhere in a condition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-54) Add mappings for scoring and userList + add score mapping in profile
[ https://issues.apache.org/jira/browse/UNOMI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-54. - > Add mappings for scoring and userList + add score mapping in profile > > > Key: UNOMI-54 > URL: https://issues.apache.org/jira/browse/UNOMI-54 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-32) Profile POST REST call overwrites existing profile in storage
[ https://issues.apache.org/jira/browse/UNOMI-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber closed UNOMI-32. Reviewed code should be good. > Profile POST REST call overwrites existing profile in storage > - > > Key: UNOMI-32 > URL: https://issues.apache.org/jira/browse/UNOMI-32 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.0.0-incubating, 1.1.0-incubating >Reporter: Serge Huber >Assignee: Thomas Draier > Fix For: 1.1.0-incubating > > Original Estimate: 4h > Remaining Estimate: 4h > > Currently, if we receive a POST request on the ProfileServiceEndPoint.save > method, we will directly save the content in ElasticSearch. The problem is > that ES by default will always replace any existing entry, meaning that if it > contained data that was not sent in the POST request then we will loose > profile data. > We need to define whether it is the responsibility of the endpoint or the > ProfileService to check for existing data and merging it, but since we > already have update methods in the back-end it seems to me that the save > method could overwrite existing data and that the endpoint could take care of > the needed logic of merging, but this is open for discussion here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-34) Add PropertyType for pageReferringURL session property
[ https://issues.apache.org/jira/browse/UNOMI-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-34. - > Add PropertyType for pageReferringURL session property > -- > > Key: UNOMI-34 > URL: https://issues.apache.org/jira/browse/UNOMI-34 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-11) Remove references to generate-package profile
[ https://issues.apache.org/jira/browse/UNOMI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-11. - > Remove references to generate-package profile > - > > Key: UNOMI-11 > URL: https://issues.apache.org/jira/browse/UNOMI-11 > Project: Apache Unomi > Issue Type: Task >Reporter: Quentin Lamerand >Priority: Minor > Fix For: 1.0.0-incubating > > > As the package project is included the root pom modules tag, it's now built > by default and there is no need for a specific profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-50) Add possibility to query sessions
[ https://issues.apache.org/jira/browse/UNOMI-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-50. - > Add possibility to query sessions > - > > Key: UNOMI-50 > URL: https://issues.apache.org/jira/browse/UNOMI-50 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-46) Avoid NPE when asking for the definition of a missing tag + Return 404
[ https://issues.apache.org/jira/browse/UNOMI-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-46. - > Avoid NPE when asking for the definition of a missing tag + Return 404 > -- > > Key: UNOMI-46 > URL: https://issues.apache.org/jira/browse/UNOMI-46 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-41) Add score modifiers
[ https://issues.apache.org/jira/browse/UNOMI-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-41. - > Add score modifiers > --- > > Key: UNOMI-41 > URL: https://issues.apache.org/jira/browse/UNOMI-41 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-33) Profile CSV export should contain custom properties as well (e.g. set by form mapping)
[ https://issues.apache.org/jira/browse/UNOMI-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-33. - > Profile CSV export should contain custom properties as well (e.g. set by form > mapping) > -- > > Key: UNOMI-33 > URL: https://issues.apache.org/jira/browse/UNOMI-33 > Project: Apache Unomi > Issue Type: Bug >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-35) Add campaigns choiceListInitializer
[ https://issues.apache.org/jira/browse/UNOMI-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quentin Lamerand closed UNOMI-35. - > Add campaigns choiceListInitializer > --- > > Key: UNOMI-35 > URL: https://issues.apache.org/jira/browse/UNOMI-35 > Project: Apache Unomi > Issue Type: Improvement >Reporter: Quentin Lamerand >Assignee: Quentin Lamerand > Fix For: 1.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-19) Rationalize dependencies management
[ https://issues.apache.org/jira/browse/UNOMI-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Laprun closed UNOMI-19. -- > Rationalize dependencies management > --- > > Key: UNOMI-19 > URL: https://issues.apache.org/jira/browse/UNOMI-19 > Project: Apache Unomi > Issue Type: Improvement > Components: build >Affects Versions: 1.0.0-incubating >Reporter: Christophe Laprun >Assignee: Serge Huber > Fix For: 1.1.0-incubating > > > We have lots of repeat versions in the POM files, we use rationalize this > using Maven's dependency management mechanism: > https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-37) Add incubator-relevant information to website
[ https://issues.apache.org/jira/browse/UNOMI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier updated UNOMI-37: --- Fix Version/s: (was: 1.1.0-incubating) 1.2.0-incubating > Add incubator-relevant information to website > - > > Key: UNOMI-37 > URL: https://issues.apache.org/jira/browse/UNOMI-37 > Project: Apache Unomi > Issue Type: Improvement > Components: website >Affects Versions: 1.1.0-incubating >Reporter: Christophe Laprun >Priority: Minor > Fix For: 1.2.0-incubating > > > See http://incubator.apache.org/guides/branding.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-60) Function getServerInfo return hardcoded version
Damien GAILLARD created UNOMI-60: Summary: Function getServerInfo return hardcoded version Key: UNOMI-60 URL: https://issues.apache.org/jira/browse/UNOMI-60 Project: Apache Unomi Issue Type: Bug Affects Versions: 1.1.0-incubating Reporter: Damien GAILLARD Fix For: 1.2.0-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-64) Add Region/State/Province and Subregion/County
[ https://issues.apache.org/jira/browse/UNOMI-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-64. Resolution: Fixed Fix Version/s: 1.2.0-incubating > Add Region/State/Province and Subregion/County > -- > > Key: UNOMI-64 > URL: https://issues.apache.org/jira/browse/UNOMI-64 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > Add Region/State/Province and Subregion/County as type definitions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-64) Add Region/State/Province and Subregion/County
Abdelkader Midani created UNOMI-64: -- Summary: Add Region/State/Province and Subregion/County Key: UNOMI-64 URL: https://issues.apache.org/jira/browse/UNOMI-64 Project: Apache Unomi Issue Type: Improvement Components: core Affects Versions: 1.2.0-incubating Reporter: Abdelkader Midani Assignee: Abdelkader Midani Add Region/State/Province and Subregion/County as type definitions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-5) Upgrade to Karaf 4
[ https://issues.apache.org/jira/browse/UNOMI-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686331#comment-15686331 ] Serge Huber commented on UNOMI-5: - JB, any update on this ? If you have a patch you could attach to this ticket, or a branch you could contribute this would be fantastic. I tried doing it myself but was running into some issues with the test subprojects. > Upgrade to Karaf 4 > -- > > Key: UNOMI-5 > URL: https://issues.apache.org/jira/browse/UNOMI-5 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > I will upgrade Unomi to use Karaf 4, especially: > - usage of new feature namespace (1.3 min) allowing to leverage the features > resolver (and so resources repositories, requirements & capabilities, etc) > - new commands > - ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-66) Integrate Apache Kafka
Serge Huber created UNOMI-66: Summary: Integrate Apache Kafka Key: UNOMI-66 URL: https://issues.apache.org/jira/browse/UNOMI-66 Project: Apache Unomi Issue Type: Bug Components: core Reporter: Serge Huber It would be really great to integrate Apache Kafka into Apache Unomi so that we can push event data and other "heavy" operations into its messaging systems and therefore make it easier to decouple some large scale operations that might require a lot of processing power such as large segment updates, etc... This would also make it a lot easier to integrate with BigData systems such as Apache Spark, Hadoop or others. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-67) Add support for Do Not Track
Serge Huber created UNOMI-67: Summary: Add support for Do Not Track Key: UNOMI-67 URL: https://issues.apache.org/jira/browse/UNOMI-67 Project: Apache Unomi Issue Type: Bug Components: core Reporter: Serge Huber As Unomi is trying to address privacy issues related to tracking, it should implement the Do Not Track specification. Here is more information about it : https://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-66) Integrate Apache Kafka
[ https://issues.apache.org/jira/browse/UNOMI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber updated UNOMI-66: - Description: It would be really great to integrate Apache Kafka into Apache Unomi so that we can push event data and other "heavy" operations into its messaging systems and therefore make it easier to decouple some large scale operations that might require a lot of processing power such as large segment updates, etc... This would also make it a lot easier to integrate with BigData systems such as Apache Spark, Hadoop or others. We might want at the same time to see if we can define a mechanism to get the status of long-running operations. was: It would be really great to integrate Apache Kafka into Apache Unomi so that we can push event data and other "heavy" operations into its messaging systems and therefore make it easier to decouple some large scale operations that might require a lot of processing power such as large segment updates, etc... This would also make it a lot easier to integrate with BigData systems such as Apache Spark, Hadoop or others. > Integrate Apache Kafka > -- > > Key: UNOMI-66 > URL: https://issues.apache.org/jira/browse/UNOMI-66 > Project: Apache Unomi > Issue Type: Bug > Components: core >Reporter: Serge Huber > > It would be really great to integrate Apache Kafka into Apache Unomi so that > we can push event data and other "heavy" operations into its messaging > systems and therefore make it easier to decouple some large scale operations > that might require a lot of processing power such as large segment updates, > etc... > This would also make it a lot easier to integrate with BigData systems such > as Apache Spark, Hadoop or others. > We might want at the same time to see if we can define a mechanism to get the > status of long-running operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-69) Externalize ElasticSearch server
Serge Huber created UNOMI-69: Summary: Externalize ElasticSearch server Key: UNOMI-69 URL: https://issues.apache.org/jira/browse/UNOMI-69 Project: Apache Unomi Issue Type: Improvement Components: core Affects Versions: 1.2.0-incubating Reporter: Serge Huber Currently we use an embedded ElasticSearch server in Unomi. This is very practical to simplify deployment, but is causing the following problems: - Starting with ES 5.0 this is no longer support by Elastic - Makes it tricky to deploy plugins - Using the same JVM for Apache Unomi and ES is not very flexible in terms of performance and scalability - Makes it impossible to use cloud-hosted ES instances. We need to perform the following tasks to externalize the ES server: - Modify the clustering code to use Karaf Cellar for cluster information - Use the ES TransportClient instead of the node client - Provide a migration path - Modify integration tests to launch an ES server before launching Karaf Despite these tasks, it shouldn't be too difficult to achieve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-68) Fix site branding
[ https://issues.apache.org/jira/browse/UNOMI-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702358#comment-15702358 ] Christophe Laprun commented on UNOMI-68: Done: https://git-wip-us.apache.org/repos/asf?p=incubator-unomi.git;a=commit;h=a4955cafac8910e266e9ea11752c1145cfb92209 > Fix site branding > - > > Key: UNOMI-68 > URL: https://issues.apache.org/jira/browse/UNOMI-68 > Project: Apache Unomi > Issue Type: Bug > Components: website >Reporter: Serge Huber > Original Estimate: 3h > Remaining Estimate: 3h > > Things I noticed: > 1. You seem to be advertising the 1.2.0 snapshot prominently on your site > (under the top menu). While there's no link it may be best to remove this? [1] > 2. While the incubator logo and disclaimer is included it's way down beneath > the fold, it could be more prominent. An ASF logo with links home page would > also be a nice to have. > 3. There’s a few Apache trademarks you might want to give attribution to like > Karaf, Fleix and Mahout. > 4. There a few pages/link missing I expected to see. [2] e.g. link to ASF > home page, sponsorship, thanks and security. > 1. http://www.apache.org/dev/release.html#what > 2. http://www.apache.org/foundation/marks/pmcs.html#navigation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-68) Fix site branding
Serge Huber created UNOMI-68: Summary: Fix site branding Key: UNOMI-68 URL: https://issues.apache.org/jira/browse/UNOMI-68 Project: Apache Unomi Issue Type: Bug Components: website Reporter: Serge Huber Things I noticed: 1. You seem to be advertising the 1.2.0 snapshot prominently on your site (under the top menu). While there's no link it may be best to remove this? [1] 2. While the incubator logo and disclaimer is included it's way down beneath the fold, it could be more prominent. An ASF logo with links home page would also be a nice to have. 3. There’s a few Apache trademarks you might want to give attribution to like Karaf, Fleix and Mahout. 4. There a few pages/link missing I expected to see. [2] e.g. link to ASF home page, sponsorship, thanks and security. 1. http://www.apache.org/dev/release.html#what 2. http://www.apache.org/foundation/marks/pmcs.html#navigation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-53) goalMatchCondition : comparisonOperator as a parameter
[ https://issues.apache.org/jira/browse/UNOMI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-53. Resolution: Fixed Fix Version/s: 1.2.0-incubating > goalMatchCondition : comparisonOperator as a parameter > -- > > Key: UNOMI-53 > URL: https://issues.apache.org/jira/browse/UNOMI-53 > Project: Apache Unomi > Issue Type: Bug > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > Instead of 'exists' as the only value, user should be able to choose between > fulfilled or not fulfilled goal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-59) Handle update of multivalued property
[ https://issues.apache.org/jira/browse/UNOMI-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-59. Resolution: Fixed > Handle update of multivalued property > - > > Key: UNOMI-59 > URL: https://issues.apache.org/jira/browse/UNOMI-59 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani >Priority: Critical > > Actually the merge on multivalued property use addAll on the collection which > extends the collection with the new values instead of replacing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-59) Handle update of multivalued property
[ https://issues.apache.org/jira/browse/UNOMI-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani updated UNOMI-59: --- Fix Version/s: 1.2.0-incubating > Handle update of multivalued property > - > > Key: UNOMI-59 > URL: https://issues.apache.org/jira/browse/UNOMI-59 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani >Priority: Critical > Fix For: 1.2.0-incubating > > > Actually the merge on multivalued property use addAll on the collection which > extends the collection with the new values instead of replacing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-51) Scoring modifiers are ignored when the score value is updated
[ https://issues.apache.org/jira/browse/UNOMI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani updated UNOMI-51: --- Fix Version/s: (was: 1.2.0-incubating) 1.1.0-incubating > Scoring modifiers are ignored when the score value is updated > - > > Key: UNOMI-51 > URL: https://issues.apache.org/jira/browse/UNOMI-51 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.1.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.1.0-incubating > > > When the score value is updated the score modifier is ignored and is not > added to the value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-56) Add setPropertyValueMultiple in setPropertyAction.json
[ https://issues.apache.org/jira/browse/UNOMI-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani updated UNOMI-56: --- Fix Version/s: 1.2.0-incubating > Add setPropertyValueMultiple in setPropertyAction.json > -- > > Key: UNOMI-56 > URL: https://issues.apache.org/jira/browse/UNOMI-56 > Project: Apache Unomi > Issue Type: Bug > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-51) Scoring modifiers are ignored when the score value is updated
[ https://issues.apache.org/jira/browse/UNOMI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-51. Resolution: Fixed > Scoring modifiers are ignored when the score value is updated > - > > Key: UNOMI-51 > URL: https://issues.apache.org/jira/browse/UNOMI-51 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.1.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > When the score value is updated the score modifier is ignored and is not > added to the value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-61) Update mvel version
[ https://issues.apache.org/jira/browse/UNOMI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628576#comment-15628576 ] Damien GAILLARD commented on UNOMI-61: -- After many tests it really difficult to reproduce the errors and searching on internet is seems that upgrading to latest version of mvel should fix the problem > Update mvel version > --- > > Key: UNOMI-61 > URL: https://issues.apache.org/jira/browse/UNOMI-61 > Project: Apache Unomi > Issue Type: Bug >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > > Sometimes when the context server is heavily loaded mvel throw an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-55) typing issue in defaultDeniedProperties (org.apache.unomi.privacy.cfg)
[ https://issues.apache.org/jira/browse/UNOMI-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD closed UNOMI-55. > typing issue in defaultDeniedProperties (org.apache.unomi.privacy.cfg) > -- > > Key: UNOMI-55 > URL: https://issues.apache.org/jira/browse/UNOMI-55 > Project: Apache Unomi > Issue Type: Bug >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.1.0-incubating > > > Tested CXS 1.1.0 #685: > - open /etc/org.apache.unomi.privacy.cfg > - the property "linedInId" has a typing issue - the "k" is missing > -> please add (linkedInId) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-61) Update mvel version
[ https://issues.apache.org/jira/browse/UNOMI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628599#comment-15628599 ] Damien GAILLARD commented on UNOMI-61: -- PR waiting to be merge https://github.com/apache/incubator-unomi/pull/17 > Update mvel version > --- > > Key: UNOMI-61 > URL: https://issues.apache.org/jira/browse/UNOMI-61 > Project: Apache Unomi > Issue Type: Bug >Affects Versions: 1.1.0-incubating, 1.2.0-incubating >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.2.0-incubating > > > Sometimes when the context server is heavily loaded mvel throw an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (UNOMI-61) Update mvel version
[ https://issues.apache.org/jira/browse/UNOMI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD resolved UNOMI-61. -- Resolution: Fixed > Update mvel version > --- > > Key: UNOMI-61 > URL: https://issues.apache.org/jira/browse/UNOMI-61 > Project: Apache Unomi > Issue Type: Bug >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > > Sometimes when the context server is heavily loaded mvel throw an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-61) Update mvel version
Damien GAILLARD created UNOMI-61: Summary: Update mvel version Key: UNOMI-61 URL: https://issues.apache.org/jira/browse/UNOMI-61 Project: Apache Unomi Issue Type: Bug Reporter: Damien GAILLARD Assignee: Damien GAILLARD Sometimes when the context server is heavily loaded mvel throw an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UNOMI-60) Function getServerInfo return hardcoded version
[ https://issues.apache.org/jira/browse/UNOMI-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD closed UNOMI-60. Resolution: Fixed Assignee: Damien GAILLARD > Function getServerInfo return hardcoded version > --- > > Key: UNOMI-60 > URL: https://issues.apache.org/jira/browse/UNOMI-60 > Project: Apache Unomi > Issue Type: Bug >Affects Versions: 1.1.0-incubating >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-51) Scoring modifiers are ignored when the score value is updated
[ https://issues.apache.org/jira/browse/UNOMI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD updated UNOMI-51: - Assignee: Abdelkader Midani > Scoring modifiers are ignored when the score value is updated > - > > Key: UNOMI-51 > URL: https://issues.apache.org/jira/browse/UNOMI-51 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.1.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > When the score value is updated the score modifier is ignored and is not > added to the value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-52) Review conditions tags
[
https://issues.apache.org/jira/browse/UNOMI-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien GAILLARD updated UNOMI-52:
-
Assignee: Abdelkader Midani
> Review conditions tags
> --
>
> Key: UNOMI-52
> URL: https://issues.apache.org/jira/browse/UNOMI-52
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
>Affects Versions: 1.1.0-incubating
>Reporter: Abdelkader Midani
>Assignee: Abdelkader Midani
> Fix For: 1.2.0-incubating
>
>
> Replace demographic tag with event ("behavioural") for new visitor, returning
> visitor, session duration, session property conditions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (UNOMI-61) Update mvel version
[ https://issues.apache.org/jira/browse/UNOMI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628576#comment-15628576 ] Damien GAILLARD edited comment on UNOMI-61 at 11/2/16 10:51 AM: After many tests it's really difficult to reproduce the errors and searching on internet is seems that upgrading to latest version of mvel should fix the problem was (Author: dgaillard): After many tests it really difficult to reproduce the errors and searching on internet is seems that upgrading to latest version of mvel should fix the problem > Update mvel version > --- > > Key: UNOMI-61 > URL: https://issues.apache.org/jira/browse/UNOMI-61 > Project: Apache Unomi > Issue Type: Bug >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > > Sometimes when the context server is heavily loaded mvel throw an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-59) Handle update of multivalued property
[ https://issues.apache.org/jira/browse/UNOMI-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD updated UNOMI-59: - Assignee: Abdelkader Midani > Handle update of multivalued property > - > > Key: UNOMI-59 > URL: https://issues.apache.org/jira/browse/UNOMI-59 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani >Priority: Critical > > Actually the merge on multivalued property use addAll on the collection which > extends the collection with the new values instead of replacing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-56) Add setPropertyValueMultiple in setPropertyAction.json
[ https://issues.apache.org/jira/browse/UNOMI-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damien GAILLARD updated UNOMI-56: - Assignee: Abdelkader Midani > Add setPropertyValueMultiple in setPropertyAction.json > -- > > Key: UNOMI-56 > URL: https://issues.apache.org/jira/browse/UNOMI-56 > Project: Apache Unomi > Issue Type: Bug > Components: core >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (UNOMI-28) Upgrade to Elasticsearch 2.x
[ https://issues.apache.org/jira/browse/UNOMI-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber updated UNOMI-28: - Assignee: Serge Huber (was: Jean-Baptiste Onofré) Affects Version/s: 1.2.0-incubating Fix Version/s: 1.2.0-incubating Component/s: core > Upgrade to Elasticsearch 2.x > > > Key: UNOMI-28 > URL: https://issues.apache.org/jira/browse/UNOMI-28 > Project: Apache Unomi > Issue Type: Task > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Jean-Baptiste Onofré >Assignee: Serge Huber > Fix For: 1.2.0-incubating > > Attachments: elasticsearch migration checker v1.18.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-28) Upgrade to Elasticsearch 2.x
[ https://issues.apache.org/jira/browse/UNOMI-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15561674#comment-15561674 ] Serge Huber commented on UNOMI-28: -- ElasticSearch 2.4.0 has added a setting to allow dots in field names again. See https://github.com/elastic/elasticsearch/pull/19937 I've updated our branch to ES 2.4 and implemented support for this setting. See here : https://github.com/apache/incubator-unomi/commit/fda0d9ce711ff189a8f4af42711d17a5d9d020ed cheers, Serge... > Upgrade to Elasticsearch 2.x > > > Key: UNOMI-28 > URL: https://issues.apache.org/jira/browse/UNOMI-28 > Project: Apache Unomi > Issue Type: Task > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 1.2.0-incubating > > Attachments: elasticsearch migration checker v1.18.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-72) Fix integration and performance tests
Serge Huber created UNOMI-72:
Summary: Fix integration and performance tests
Key: UNOMI-72
URL: https://issues.apache.org/jira/browse/UNOMI-72
Project: Apache Unomi
Issue Type: Bug
Components: core
Affects Versions: 1.2.0-incubating
Reporter: Serge Huber
Fix For: 1.2.0-incubating
Since we moved to ElasticSearch 5.x and externalized the ES server, the
integration and performance tests are broken. We should fix them but this is
not easy since we need to somehow startup an ES server.
We tried using the following pom.xml plugin configuration :
{code}
com.github.alexcojocaru
elasticsearch-maven-plugin
5.0
contextElasticSearch
9300
9200
5.0.2
start-elasticsearch
pre-integration-test
runforked
stop-elasticsearch
post-integration-test
stop
org.apache.maven.plugins
maven-failsafe-plugin
**/*AllITs.java
integration-test
verify
{code}
but it fails with the following errors :
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 04:08 min
[INFO] Finished at: 2017-01-10T20:55:49+01:00
[INFO] Final Memory: 96M/919M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test
(default) on project unomi-itests: Execution default of goal
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test failed:
The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was /bin/sh -c cd
/Users/loom/java/technologies/apache-git/incubator-unomi/itests &&
/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/jre/bin/java
-jar
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefirebooter410416926696253620.jar
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire3550479375448672288tmp
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire_0105027550392275185tmp
[ERROR] -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (UNOMI-72) Fix integration and performance tests
[
https://issues.apache.org/jira/browse/UNOMI-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816013#comment-15816013
]
Serge Huber commented on UNOMI-72:
--
For the moment I deactivated the default execution of the tests until we can
fix them.
> Fix integration and performance tests
> -
>
> Key: UNOMI-72
> URL: https://issues.apache.org/jira/browse/UNOMI-72
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.0-incubating
>Reporter: Serge Huber
> Fix For: 1.2.0-incubating
>
>
> Since we moved to ElasticSearch 5.x and externalized the ES server, the
> integration and performance tests are broken. We should fix them but this is
> not easy since we need to somehow startup an ES server.
> We tried using the following pom.xml plugin configuration :
> {code}
>
> com.github.alexcojocaru
> elasticsearch-maven-plugin
>
> 5.0
>
> contextElasticSearch
> 9300
> 9200
> 5.0.2
>
>
>
>
> start-elasticsearch
> pre-integration-test
>
> runforked
>
>
>
> stop-elasticsearch
> post-integration-test
>
> stop
>
>
>
>
>
> org.apache.maven.plugins
> maven-failsafe-plugin
>
>
> **/*AllITs.java
>
>
>
>
>
> integration-test
> verify
>
>
>
>
> {code}
> but it fails with the following errors :
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:08 min
> [INFO] Finished at: 2017-01-10T20:55:49+01:00
> [INFO] Final Memory: 96M/919M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test
> (default) on project unomi-itests: Execution default of goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test
> failed: The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was /bin/sh -c cd
> /Users/loom/java/technologies/apache-git/incubator-unomi/itests &&
> /Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/jre/bin/java
> -jar
> /Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefirebooter410416926696253620.jar
>
> /Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire3550479375448672288tmp
>
> /Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire_0105027550392275185tmp
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (UNOMI-70) Upgrade to ElasticSearch 5.x
Serge Huber created UNOMI-70: Summary: Upgrade to ElasticSearch 5.x Key: UNOMI-70 URL: https://issues.apache.org/jira/browse/UNOMI-70 Project: Apache Unomi Issue Type: Bug Components: core Affects Versions: 1.2.0-incubating Reporter: Serge Huber Assignee: Serge Huber Fix For: 1.2.0-incubating I've started work on migrating Apache Unomi to ElasticSearch 5.x, along with the "externalization" of the ElasticSearch server. Until now we have been embedding the ES server, but as this is no longer supported by Elastic (see https://www.elastic.co/blog/elasticsearch-the-server), and also because it is interesting to free up Unomi's JVM from ES work, my work will also modify the clustering implementation to use Karaf Cellar instead of depending on ES' clustering. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UNOMI-71) Improve startup and test if ES server is available before trying to start Unomi services
Damien GAILLARD created UNOMI-71: Summary: Improve startup and test if ES server is available before trying to start Unomi services Key: UNOMI-71 URL: https://issues.apache.org/jira/browse/UNOMI-71 Project: Apache Unomi Issue Type: Sub-task Reporter: Damien GAILLARD Priority: Minor As today we do not test if ES server is available/started which result in a crash of the Unomi server, this can be easily avoid by making sure that your ES server is started however it will be nice to improve the startup process of Unomi to avoid logging exception and instead logging a human readable message saying that you need an instance of ES server in order to start your Unomi server. Also the server should try to restart by checking if the server is available every X minutes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UNOMI-88) Display Impression and Click Tracking
[ https://issues.apache.org/jira/browse/UNOMI-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940244#comment-15940244 ] Serge Huber commented on UNOMI-88: -- Hello, Yes I believe you could use Unomi for this purpose. The sessionId requirement is actually something we must change to make it optional, since it is allowed to create sessions on the fly using the /context.js(on) call. Another way of doing it would be to actually track the context when loading the add, and then sending an event using the event collector. This way you could also personalize the page based on the loaded profile if the user comes back, or serve different ads. Regards, Serge... > Display Impression and Click Tracking > - > > Key: UNOMI-88 > URL: https://issues.apache.org/jira/browse/UNOMI-88 > Project: Apache Unomi > Issue Type: New Feature >Reporter: Damon Henry >Priority: Minor > > Can Unomi be used to track display advertising impressions and clicks? > A common use case is the ability to embed 1x1 image pixels in banner ad > creative to track when a banner has been viewed. A second use case it to use > a redirect (e.g. http://myserver.com?redirect=http://somesite.com) in the > banner ad creative to record when a link in an ad has been clicked. > I investigated the /eventcollector endpoint but it appears a sessionId must > appended prior which isn't possible if JavaScript tags are not supported by > the ad server. Assuming the sessionId can be created by Unomi (every banner > ad impression would be unique session), I'm unclear on how the event payload > should supplied to the /eventcollector endpoint. > Any direction you can provide is appreciated if Unomi can support this use > case. > Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (UNOMI-88) Display Impression and Click Tracking
[
https://issues.apache.org/jira/browse/UNOMI-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940244#comment-15940244
]
Serge Huber edited comment on UNOMI-88 at 3/24/17 12:43 PM:
Hello,
Yes I believe you could use Unomi for this purpose. The sessionId requirement
is actually something we must change to make it optional, since it is allowed
to create sessions on the fly using the /context.js(on) call.
Another way of doing it would be to actually track the context when loading the
add, and then sending an event using the event collector. This way you could
also personalize the page based on the loaded profile if the user comes back,
or serve different ads.
Providing the event payload is just a matter of providing a JSON payload with
the proper structure. So basically something like this:
var scope = 'unomi-tweet-button-sample';
var itemId = btoa(window.location.href);
var source = {
itemType: 'page',
scope: scope,
itemId: itemId,
properties: {
url: window.location.href
}
};
var eventsPayload = {
events: [
{
eventType: 'tweetEvent',
scope: scope,
source: source
}
]
};
These are actually direct JSON versions of the Java objects defined in the API
here:
http://unomi.incubator.apache.org/unomi-api/apidocs/org/apache/unomi/api/EventsCollectorRequest.html
Regards,
Serge...
was (Author: shuber):
Hello,
Yes I believe you could use Unomi for this purpose. The sessionId requirement
is actually something we must change to make it optional, since it is allowed
to create sessions on the fly using the /context.js(on) call.
Another way of doing it would be to actually track the context when loading the
add, and then sending an event using the event collector. This way you could
also personalize the page based on the loaded profile if the user comes back,
or serve different ads.
Regards,
Serge...
> Display Impression and Click Tracking
> -
>
> Key: UNOMI-88
> URL: https://issues.apache.org/jira/browse/UNOMI-88
> Project: Apache Unomi
> Issue Type: New Feature
>Reporter: Damon Henry
>Priority: Minor
>
> Can Unomi be used to track display advertising impressions and clicks?
> A common use case is the ability to embed 1x1 image pixels in banner ad
> creative to track when a banner has been viewed. A second use case it to use
> a redirect (e.g. http://myserver.com?redirect=http://somesite.com) in the
> banner ad creative to record when a link in an ad has been clicked.
> I investigated the /eventcollector endpoint but it appears a sessionId must
> appended prior which isn't possible if JavaScript tags are not supported by
> the ad server. Assuming the sessionId can be created by Unomi (every banner
> ad impression would be unique session), I'm unclear on how the event payload
> should supplied to the /eventcollector endpoint.
> Any direction you can provide is appreciated if Unomi can support this use
> case.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (UNOMI-88) Display Impression and Click Tracking
[ https://issues.apache.org/jira/browse/UNOMI-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940401#comment-15940401 ] Damon Henry commented on UNOMI-88: -- If I'm following, your example of personalizing the page (or ad) is more relevant to the publisher side. The use case I described is targeted at the ad buying side. I don't think I can track the context on ad load in the buying scenario because, in some cases, 1x1 images pixels are the only tracking mechanism supported (not JavaScript). I've successfully implemented the event payload with JavaScript but unclear how this would be using with the /eventcollector. Should the JSON payload be encoded and associated with URL parameter? > Display Impression and Click Tracking > - > > Key: UNOMI-88 > URL: https://issues.apache.org/jira/browse/UNOMI-88 > Project: Apache Unomi > Issue Type: New Feature >Reporter: Damon Henry >Priority: Minor > > Can Unomi be used to track display advertising impressions and clicks? > A common use case is the ability to embed 1x1 image pixels in banner ad > creative to track when a banner has been viewed. A second use case it to use > a redirect (e.g. http://myserver.com?redirect=http://somesite.com) in the > banner ad creative to record when a link in an ad has been clicked. > I investigated the /eventcollector endpoint but it appears a sessionId must > appended prior which isn't possible if JavaScript tags are not supported by > the ad server. Assuming the sessionId can be created by Unomi (every banner > ad impression would be unique session), I'm unclear on how the event payload > should supplied to the /eventcollector endpoint. > Any direction you can provide is appreciated if Unomi can support this use > case. > Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-88) Display Impression and Click Tracking
Damon Henry created UNOMI-88: Summary: Display Impression and Click Tracking Key: UNOMI-88 URL: https://issues.apache.org/jira/browse/UNOMI-88 Project: Apache Unomi Issue Type: New Feature Reporter: Damon Henry Priority: Minor Can Unomi be used to track display advertising impressions and clicks? A common use case is the ability to embed 1x1 image pixels in banner ad creative to track when a banner has been viewed. A second use case it to use a redirect (e.g. http://myserver.com?redirect=http://somesite.com) in the banner ad creative to record when a link in an ad has been clicked. I investigated the /eventcollector endpoint but it appears a sessionId must appended prior which isn't possible if JavaScript tags are not supported by the ad server. Assuming the sessionId can be created by Unomi (every banner ad impression would be unique session), I'm unclear on how the event payload should supplied to the /eventcollector endpoint. Any direction you can provide is appreciated if Unomi can support this use case. Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-88) Display Impression and Click Tracking
[
https://issues.apache.org/jira/browse/UNOMI-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941618#comment-15941618
]
Serge Huber commented on UNOMI-88:
--
Ok I think I understand what you're doing now.
Basically when serving an ad or a 1x1 image, you can generate the events to the
event collector. Until we fix the session requirement issue you could also
first load the context and create a session with something like this :
GET http://localhost:8181/cluster.json?sessionId=GENERATED_SESSION_ID
and then when calling the event collector you would simply do something like
POST http://localhost:8181/eventcollector?sessionId=GENERATED_SESSION_ID
In Javascript it would be something like this for the event collector payload:
data = JSON.stringify(events);
var url = "http://localhost:8181/eventcollector?sessionId=; +
generatedSessionId;
var xhr = new XMLHttpRequest();
var isGet = data.length < 100;
if ("withCredentials" in xhr) {
xhr.open("POST", url, true);
xhr.withCredentials = true;
} else if (typeof XDomainRequest != "undefined") {
xhr = new XDomainRequest();
xhr.open("POST", url);
}
xhr.onreadystatechange = function () {
if (xhr.readyState != 4) {
return;
}
if (xhr.status == 200) {
var jsonResponse = JSON.parse(xhr.responseText);
successCallBack(xhr);
} else {
console.log("contextserver: " + xhr.status + " ERROR: " +
xhr.statusText);
if (errorCallback) {
errorCallback(xhr);
}
}
};
xhr.setRequestHeader("Content-Type", "text/plain;charset=UTF-8"); // Use
text/plain to avoid CORS preflight
xhr.send(data);
I hope this help.
Regards,
Serge...
> Display Impression and Click Tracking
> -----
>
> Key: UNOMI-88
> URL: https://issues.apache.org/jira/browse/UNOMI-88
> Project: Apache Unomi
> Issue Type: New Feature
>Reporter: Damon Henry
>Priority: Minor
>
> Can Unomi be used to track display advertising impressions and clicks?
> A common use case is the ability to embed 1x1 image pixels in banner ad
> creative to track when a banner has been viewed. A second use case it to use
> a redirect (e.g. http://myserver.com?redirect=http://somesite.com) in the
> banner ad creative to record when a link in an ad has been clicked.
> I investigated the /eventcollector endpoint but it appears a sessionId must
> appended prior which isn't possible if JavaScript tags are not supported by
> the ad server. Assuming the sessionId can be created by Unomi (every banner
> ad impression would be unique session), I'm unclear on how the event payload
> should supplied to the /eventcollector endpoint.
> Any direction you can provide is appreciated if Unomi can support this use
> case.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (UNOMI-89) Add an endpoint/Service for userLists metadatas
[ https://issues.apache.org/jira/browse/UNOMI-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-89. Resolution: Fixed > Add an endpoint/Service for userLists metadatas > --- > > Key: UNOMI-89 > URL: https://issues.apache.org/jira/browse/UNOMI-89 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > Add the endpoint and the service to retrieve the userLists metadatas -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-89) Add an endpoint/Service for userLists metadatas
Abdelkader Midani created UNOMI-89: -- Summary: Add an endpoint/Service for userLists metadatas Key: UNOMI-89 URL: https://issues.apache.org/jira/browse/UNOMI-89 Project: Apache Unomi Issue Type: Improvement Components: core Affects Versions: 1.2.0-incubating Reporter: Abdelkader Midani Assignee: Abdelkader Midani Fix For: 1.2.0-incubating Add the endpoint and the service to retrieve the userLists metadatas -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (UNOMI-81) Add entry point to Definitions service to allow tag creation
[ https://issues.apache.org/jira/browse/UNOMI-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947491#comment-15947491 ] Damien GAILLARD commented on UNOMI-81: -- reverted, as discussed we will implement another solution > Add entry point to Definitions service to allow tag creation > > > Key: UNOMI-81 > URL: https://issues.apache.org/jira/browse/UNOMI-81 > Project: Apache Unomi > Issue Type: Improvement >Affects Versions: 1.2.0-incubating >Reporter: Damien GAILLARD >Assignee: Damien GAILLARD > Fix For: 1.2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (UNOMI-87) Rewrite the queries for the scroring plans update
Abdelkader Midani created UNOMI-87: -- Summary: Rewrite the queries for the scroring plans update Key: UNOMI-87 URL: https://issues.apache.org/jira/browse/UNOMI-87 Project: Apache Unomi Issue Type: Improvement Components: core Affects Versions: 1.2.0-incubating Reporter: Abdelkader Midani Assignee: Abdelkader Midani Fix For: 1.2.0-incubating Queries for the scoring plans update should be rewritten to be ES 5 compliant and Groovy Scripts should be converted to Painless Scripts -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (UNOMI-87) Rewrite the queries for the scroring plans update
[ https://issues.apache.org/jira/browse/UNOMI-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdelkader Midani resolved UNOMI-87. Resolution: Fixed > Rewrite the queries for the scroring plans update > - > > Key: UNOMI-87 > URL: https://issues.apache.org/jira/browse/UNOMI-87 > Project: Apache Unomi > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0-incubating >Reporter: Abdelkader Midani >Assignee: Abdelkader Midani > Fix For: 1.2.0-incubating > > > Queries for the scoring plans update should be rewritten to be ES 5 compliant > and Groovy Scripts should be converted to Painless Scripts -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (UNOMI-90) Empty sessionId is processed as a valid sessionId instead of being ignored.
[ https://issues.apache.org/jira/browse/UNOMI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Huber closed UNOMI-90. > Empty sessionId is processed as a valid sessionId instead of being ignored. > --- > > Key: UNOMI-90 > URL: https://issues.apache.org/jira/browse/UNOMI-90 > Project: Apache Unomi > Issue Type: Bug > Components: core >Affects Versions: 1.1.0-incubating, 1.2.0-incubating >Reporter: Serge Huber >Assignee: Serge Huber > Fix For: 1.2.0-incubating > > > If a context request is performed using a request such as : > http://localhost:8181/context.js?sessionId= > (note the missing sessionId) > It will store a session with the ID "" (empty) instead of treating it as an > invalid or inexistant sessionId ! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
