svn commit: r985990 - in /websites/staging/jena/trunk/content: ./ documentation/query/text-query.html

[bu...@apache.org]

Author: buildbot
Date: Mon Apr 18 11:30:20 2016
New Revision: 985990

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/query/text-query.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 18 11:30:20 2016
@@ -1 +1 @@
-1738574
+1739744

Modified: websites/staging/jena/trunk/content/documentation/query/text-query.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/text-query.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/text-query.html Mon Apr 18 11:30:20 2016
@@ -477,6 +477,21 @@ the <code>TextIndexLucene</code> resourc
 </pre></div>
 
 
+<h4 id="alternative-query-parsers">Alternative Query Parsers<a class="headerlink" href="#alternative-query-parsers" title="Permanent link">&para;</a></h4>
+<p>New in Jena 3.1.0.</p>
+<p>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 <code>TextIndexLucene</code> resource:</p>
+<div class="codehilite"><pre><span class="o">&lt;</span>#<span class="n">indexLucene</span><span class="o">&gt;</span> <span class="n">a</span> <span class="n">text</span><span class="p">:</span><span class="n">TextIndexLucene</span> <span class="p">;</span>
+    <span class="n">text</span><span class="p">:</span><span class="n">directory</span> <span class="o">&lt;</span><span class="n">file</span><span class="p">:</span><span class="n">Lucene</span><span class="o">&gt;</span> <span class="p">;</span>
+    <span class="n">text</span><span class="p">:</span><span class="n">entityMap</span> <span class="o">&lt;</span>#<span class="n">entMap</span><span class="o">&gt;</span> <span class="p">;</span>
+    <span class="n">text</span><span class="p">:</span><span class="n">queryParser</span> <span class="n">text</span><span class="p">:</span><span class="n">AnalyzingQueryParser</span> <span class="p">.</span>
+</pre></div>
+
+
 <h3 id="configuration-by-code">Configuration by Code<a class="headerlink" href="#configuration-by-code" title="Permanent link">&para;</a></h3>
 <p>A text dataset can also be constructed in code as might be done for a
 purely in-memory setup:</p>