[ 
https://issues.apache.org/jira/browse/UNOMI-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840119#comment-16840119
 ] 

Serge Huber commented on UNOMI-230:
-----------------------------------

Hello Jonathan, thanks for your interest in Unomi and especially for your 
feedback.

I think this means we really need to get 1.4.0 out the door as soon as possible 
(which is the current plan). 

I would love to know a little more what kind of use cases you have for querying 
events ? Usually querying events is not necessarily something you want to do 
"in real time" as it involves search in ElasticSearch that could slow down 
overall performance. Unomi makes it possible to associate rules with events 
that can then be used to update the profile with information you might need in 
real-time, such as page counts, number of products viewed, etc... Knowing more 
about what you are trying to achieve might make it easier to write 
documentation that can be relevant to your needs.

Regards,
  Serge Huber.

> Better documentation for searches in Unomi
> ------------------------------------------
>
>                 Key: UNOMI-230
>                 URL: https://issues.apache.org/jira/browse/UNOMI-230
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: website
>            Reporter: Casey Sybrandy
>            Priority: Major
>
> Hello,
> I've been using Unomi on a project and while I can create user profiles, I'm 
> having issues with searches because the documentation is lacking in examples. 
>  I've resorted to working around this by digging through the source tree 
> looking at code and JSON files used for tests.  That was the only way I could 
> see what query types were available.  (contains, equals, etc.)
> It's highly suggested that these search APIs are documented better, including 
> examples, so that future users can more quickly create and execute valid 
> queries without as much trial and error and/or digging.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to