You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2017/01/17 17:17:07 UTC
svn commit: r1005114 - in /websites/staging/jena/trunk/content: ./
documentation/query/arq-query-eval.html
Author: buildbot
Date: Tue Jan 17 17:17:06 2017
New Revision: 1005114
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/query/arq-query-eval.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan 17 17:17:06 2017
@@ -1 +1 @@
-1779217
+1779218
Modified: websites/staging/jena/trunk/content/documentation/query/arq-query-eval.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/arq-query-eval.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/arq-query-eval.html Tue Jan 17 17:17:06 2017
@@ -177,7 +177,7 @@ like RDF. There is a common implementati
written for a read-only data source. Basic find works well is many
cases, and the whole Jena API will be able to use the extension.
For higher SPARQL performance, ARQ can be extended at the
-<a href="#stage-generator">basic graph matching</a> or
+<a href="#graph-matching-and-a-custom-stagegenerator">basic graph matching</a> or
<a href="#opexecutor">algebra level</a>.</p>
<p>Applications writers who extend ARQ at the query execution level
should be prepared to work with the source code for ARQ for
@@ -186,7 +186,7 @@ found in the <code>src-examples</code> d
<ul>
<li><a href="#overview">Overview of ARQ Query processing-</a></li>
<li><a href="#main-query-engine">The Main Query Engine</a></li>
-<li><a href="#stage-generator">Graph matching and a custom StageGenerator</a></li>
+<li><a href="#graph-matching-and-a-custom-stagegenerator">Graph matching and a custom StageGenerator</a></li>
<li><a href="#opexecutor">OpExecutor</a></li>
<li><a href="#quads">Quads</a></li>
<li><a href="#mixed-datasets">Mixed Graph Implementation Datasets</a></li>