[
https://issues.apache.org/jira/browse/UNOMI-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843101#comment-16843101
]
Serge Huber commented on UNOMI-230:
-----------------------------------
Thank you for your detailed feedback Casey & Jonathan.
I tend to agree that being independent from the backend implementation is a
good thing but it can be complicated to achieve in a truly portable way. The
more we abstract features that may only exist in ElasticSearch the more
difficult it would be to reproduce them with another backend.
This being said I am not sure if you are aware of this but we do have some
basic support for aggregations in the query endpoint. I suggest you look at it
to see if it could cover some of your needs. It is an endpoint I think that
could be expanded, or used as a basis to expand other endpoints.
One thing I have learned building the query system is that making queries that
operate across multiple types (basically joins) is extremely complex to achieve
and can use lots of resources so I tend now to prefer adding type specific
querying and therefore prefer to expand on the session, profile and event
endpoint querying and aggregating capabilities. How does that sound ?
There is also some possibilities to do searches on sessions that could also
help but maybe you’ve already looked at that?
Regards,
Serge
> 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
> Affects Versions: 1.0.0-incubating, 1.1.0-incubating, 1.2.0-incubating,
> 1.3.0-incubating, 1.4.0
> Reporter: Casey Sybrandy
> Priority: Major
> Fix For: 1.5.0
>
>
> 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)
