Author: buildbot
Date: Sun May 21 13:39:23 2017
New Revision: 1012610
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 May 21 13:39:23 2017
@@ -1 +1 @@
-1794967
+1795700
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
May 21 13:39:23 2017
@@ -162,7 +162,7 @@ h2:hover > .headerlink, h3:hover > .head
SPARQL queries. Text indexes are additional information for
accessing the RDF graph.</p>
<p>The text index can be either <a href="http://lucene.apache.org/core";>Apache
Lucene</a> for a
-same-machine text index, or <a href="http://lucene.apache.org/solr/";>Apache
Solr</a>
+same-machine text index, or <a href="https://www.elastic.co/";>Elasticsearch</a>
for a large scale enterprise search application.</p>
<p>Some example code is <a
href="https://github.com/apache/jena/tree/master/jena-text/src/main/java/examples/";>available
here</a>.</p>
<p>This module is not compatible with the much older LARQ module.</p>
@@ -207,7 +207,7 @@ external content with only additional RD
<p>The text index uses the native query language of the index:
<a
href="http://lucene.apache.org/core/4_1_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description";>Lucene
query format</a>
or
-<a href="http://wiki.apache.org/solr/SolrQuerySyntax";>Solr query
format</a>.</p>
+<a
href="https://www.elastic.co/guide/en/elasticsearch/reference/5.2/query-dsl.html";>Elasticsearch
query format</a>.</p>
<p>A text-supporting dataset is configured with a description of which
properties work with. When data is added, any properties matching the
description cause an entry to be added from analysed text from the triple
@@ -226,7 +226,7 @@ dataset with the document metadata can b
content by URI.</p>
<p>The maintenance of the index is external to the RDF data store.</p>
<h3 id="external-applications">External applications<a class="headerlink"
href="#external-applications" title="Permanent link">¶</a></h3>
-<p>By using Solr, in either pattern A (RDF data indexed) or pattern B
+<p>By using Elasticsearch, in either pattern A (RDF data indexed) or pattern B
(external content indexed), other applications can share the
text index with SPARQL search.</p>
<h2 id="query-with-sparql">Query with SPARQL<a class="headerlink"
href="#query-with-sparql" title="Permanent link">¶</a></h2>
@@ -311,10 +311,10 @@ used to restrict the items found still f
<a href="../assembler/index.html">Jena assembler description</a>.
Configurations can
also be built with code. The assembler describes a 'text
dataset' which has an underlying RDF dataset and a text index. The text
-index describes the text index technology (Lucene or Solr) and the details
+index describes the text index technology (Lucene or Elasticsearch) and the
details
needed for for each.</p>
<p>A text index has an "entity map" which defines the properties to
-index, the name of the lucene/solr field and field used for storing the URI
+index, the name of the Lucene/Elasticsearch field and field used for storing
the URI
itself.</p>
<p>For common RDF use, there will be one field, mapping a property to a text
index field. More complex setups, with multiple properties per entity
@@ -342,8 +342,8 @@ indexed as well.</p>
<span class="n">text</span><span class="p">:</span><span
class="n">TextDataset</span> <span class="n">rdfs</span><span
class="p">:</span><span class="n">subClassOf</span> <span
class="n">ja</span><span class="p">:</span><span class="n">RDFDataset</span>
<span class="p">.</span>
# <span class="n">Lucene</span> <span class="n">index</span>
<span class="n">text</span><span class="p">:</span><span
class="n">TextIndexLucene</span> <span class="n">rdfs</span><span
class="p">:</span><span class="n">subClassOf</span> <span
class="n">text</span><span class="p">:</span><span class="n">TextIndex</span>
<span class="p">.</span>
-# <span class="n">Solr</span> <span class="n">index</span>
-<span class="n">text</span><span class="p">:</span><span
class="n">TextIndexSolr</span> <span class="n">rdfs</span><span
class="p">:</span><span class="n">subClassOf</span> <span
class="n">text</span><span class="p">:</span><span class="n">TextIndex</span>
<span class="p">.</span>
+# <span class="n">Elasticsearch</span> <span class="n">index</span>
+<span class="n">text</span><span class="p">:</span><span
class="n">TextIndexES</span> <span class="n">rdfs</span><span
class="p">:</span><span class="n">subClassOf</span> <span
class="n">text</span><span class="p">:</span><span class="n">TextIndex</span>
<span class="p">.</span>
## <span
class="o">---------------------------------------------------------------</span>
## <span class="n">This</span> <span class="n">URI</span> <span
class="n">must</span> <span class="n">be</span> <span class="n">fixed</span>
<span class="o">-</span> <span class="n">it</span><span
class="o">'</span><span class="n">s</span> <span class="n">used</span>
<span class="n">to</span> <span class="n">assemble</span> <span
class="n">the</span> <span class="n">text</span> <span
class="n">dataset</span><span class="p">.</span>
@@ -391,10 +391,9 @@ needs to identify the text dataset by it
<code>http://localhost/jena_example/#text_dataset</code>.</p>
<h3 id="configuring-an-analyzer">Configuring an Analyzer<a class="headerlink"
href="#configuring-an-analyzer" title="Permanent link">¶</a></h3>
<p>Text to be indexed is passed through a text analyzer that divides it into
tokens
-and may perform other transformations such as eliminating stop words. If a
Solr text
-index is used, the analyzer used is determined by the Solr configuration.
-If a Lucene text index is used, then by default a
<code>StandardAnalyzer</code> is used. However,
-it can be replaced by another analyzer with the <code>text:analyzer</code>
property.
+and may perform other transformations such as eliminating stop words. If a
Lucene
+or Elasticsearch text index is used, then by default a
<code>StandardAnalyzer</code> is used.
+However, it can be replaced by another analyzer with the
<code>text:analyzer</code> property.
For example with a <code>SimpleAnalyzer</code>: </p>
<div class="codehilite"><pre><span class="o"><</span>#<span
class="n">indexLucene</span><span class="o">></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"><</span><span
class="n">file</span><span class="p">:</span><span class="n">Lucene</span><span
class="o">></span> <span class="p">;</span>
@@ -497,6 +496,7 @@ the <code>TextIndexLucene</code> resourc
</pre></div>
+<p>Elasticsearch currently doesn't support Analyzers beyond Standard Analyzer.
</p>
<h3 id="configuration-by-code">Configuration by Code<a class="headerlink"
href="#configuration-by-code" title="Permanent link">¶</a></h3>
<p>A text dataset can also be constructed in code as might be done for a
purely in-memory setup:</p>
@@ -850,7 +850,17 @@ then use the following maven dependency:
<p>adjusting the version <code>X.Y.Z</code> as necessary. This will
automatically
-include a compatible version of Lucene and the Solr java client, but not Solr
server.</p>
+include a compatible version of Lucene.</p>
+<p>For Elasticsearch implementation, you can include the following Maven
Dependency:</p>
+<div class="codehilite"><pre><span class="nt"><dependency></span>
+ <span class="nt"><groupId></span>org.apache.jena<span
class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>jena-text-es<span
class="nt"></artifactId></span>
+ <span class="nt"><version></span>X.Y.Z<span
class="nt"></version></span>
+<span class="nt"></dependency></span>
+</pre></div>
+
+
+<p>adjusting the version <code>X.Y.Z</code> as necessary.</p>
</div>
</div>
