[
https://issues.apache.org/jira/browse/UNOMI-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841231#comment-16841231
]
Casey Sybrandy commented on UNOMI-230:
--------------------------------------
Serge,
I personally like the idea of having the aggregations be accessible through
Unomi vs. directly connecting to ElasticSearch. First, any product that
already leverages Unomi can leverage the same connection to perform the
aggregations vs. having to create a second connection to ElasticSearch.
Second, if for some reason you move from ElasticSearch to another data store in
the future, the transition is more seamless for the customers.
However, I state this assuming that such operations are within the desired
scope of functionality for Unomi.
> 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)
