You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by os...@apache.org on 2016/04/18 13:29:56 UTC

svn commit: r1739744 - /jena/site/trunk/content/documentation/query/text-query.mdtext

Author: osma
Date: Mon Apr 18 11:29:55 2016
New Revision: 1739744

URL: http://svn.apache.org/viewvc?rev=1739744&view=rev
Log:
documentation for JENA-1134: using AnalyzingQueryParser for jena-text

Modified:
    jena/site/trunk/content/documentation/query/text-query.mdtext

Modified: jena/site/trunk/content/documentation/query/text-query.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/text-query.mdtext?rev=1739744&r1=1739743&r2=1739744&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/text-query.mdtext (original)
+++ jena/site/trunk/content/documentation/query/text-query.mdtext Mon Apr 18 11:29:55 2016
@@ -335,6 +335,23 @@ the `TextIndexLucene` resource:
         ]
         .
 
+#### Alternative Query Parsers
+
+New in Jena 3.1.0.
+
+It is possible to select another query parser (currently only
+AnalyzingQueryParser is supported) instead of the default QueryParser. The
+main difference between these query parsers is that AnalyzingQueryParser
+performs analysis also for wildcard queries. This is useful in combination
+with accent-insensitive wildcard queries. The query parser is specified on
+the `TextIndexLucene` resource:
+
+    <#indexLucene> a text:TextIndexLucene ;
+        text:directory <file:Lucene> ;
+        text:entityMap <#entMap> ;
+        text:queryParser text:AnalyzingQueryParser .
+
+
 ### Configuration by Code
 
 A text dataset can also be constructed in code as might be done for a