You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Daniel Siviter (JIRA)" <ji...@apache.org> on 2017/03/20 11:07:41 UTC

[jira] [Created] (IGNITE-4841) Improve TEXT Query Documentation

Daniel Siviter created IGNITE-4841:
--------------------------------------

             Summary: Improve TEXT Query Documentation
                 Key: IGNITE-4841
                 URL: https://issues.apache.org/jira/browse/IGNITE-4841
             Project: Ignite
          Issue Type: Improvement
          Components: documentation
    Affects Versions: 1.9
            Reporter: Daniel Siviter


The documentation for Full TEXT Queries is thin at best:
* What syntax does it use?
* ...is it the full [Lucene Classic Query Parser Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
* ...if so how does the syntax map to the {{@QueryTextField}} annotation?
* How is Lucene analyser customisation performed?
* What version is supported? (looks like 3.5.0 which is pretty old, latest is 6.4.1)
* The [{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html] JavaDoc refers to [{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html] but strangely this doesn't even appear in the official JavaDoc. It is because it's an 'internal' class?

It's mentioned multiple times as a feature, but doesn't look like much of Lucene can actually be utilised so clarifications would help greatly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)