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

[bu...@apache.org]

Author: buildbot
Date: Sun Dec 10 16:28:18 2017
New Revision: 1022017

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 Sun Dec 10 16:28:18 2017
@@ -1 +1 @@
-1817114
+1817721

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 Sun Dec 10 16:28:18 2017
@@ -559,10 +559,6 @@ in graph, <code>ex:G2</code>.</p>
 
 <p>will iterate over the graphs in the dataset, searching each in turn for
 matches.</p>
-<p>Note that there is a known issue when a <code>lang:xx</code> argument is included in
-the above pattern, so that the restriction to given language is not obeyed. 
-This will be corrected in a future release. However, use of a language tag
-on the <code>query string</code> is not subject to this issue.</p>
 <p>If there is suitable structure to the graphs, e.g., a known <code>rdf:type</code> and
 depending on the selectivity of the text query and number of graphs, 
 it may be more performant to express the query as follows:</p>
@@ -574,8 +570,6 @@ it may be more performant to express the
 </pre></div>
 
 
-<p>Note that this form does not have any issue with <code>lang:xx</code> as described
-above, since the graph is extracted after the text search.</p>
 <h4 id="queries-across-multiple-fields">Queries across multiple <code>Field</code>s<a class="headerlink" href="#queries-across-multiple-fields" title="Permanent link">&para;</a></h4>
 <p>As mentioned earlier, the text index uses the
 <a href="http://lucene.apache.org/core/6_4_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description">native Lucene query language</a>;