You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Kim Ahlstrøm <an...@apache.org> on 2017/01/17 10:38:18 UTC
CMS diff: ARQ - Extending Query Execution
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Farq-query-eval.mdtext
Kim Ahlstr�m
Index: trunk/content/documentation/query/arq-query-eval.mdtext
===================================================================
--- trunk/content/documentation/query/arq-query-eval.mdtext (revision 1655891)
+++ trunk/content/documentation/query/arq-query-eval.mdtext (working copy)
@@ -3,7 +3,7 @@
This page describes the mechanisms that can be used to extend and
modify query execution within ARQ. Through these mechanisms, ARQ
can be used to query different graph implementations and to provide
-different query evaluation and opti-mization strategies for
+different query evaluation and optimization strategies for
particular circumstances. These mechanisms are used by
[TDB-](../tdb) and [SDB](../sdb/).-
@@ -19,12 +19,12 @@
Jena itself can be extended by providing a new implementation of
the `Graph` interface. This can be used to encapsulate specific
specialised storage and also for wrapping non-RDF sources to look
-like RDF. There is a common implementation framewo-fk provided-fby
+like RDF. There is a common implementation framework provided by
`GraphBase` so only one operation, the `find` method, needs to be
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
-[basic graph matching](#stage-generator) or
+[basic graph matching](#graph-matching-and-a-custom-stagegenerator) or
[algebra level](#opexecutor).
Applications writers who extend ARQ at the query execution level
@@ -34,7 +34,7 @@
- [Overview of ARQ Query processing-](#overview)
- [The Main Query Engine](#main-query-engine)
-- [Graph matching and a custom StageGenerator](#stage-generator)
+- [Graph matching and a custom StageGenerator](#graph-matching-and-a-custom-stagegenerator)
- [OpExecutor](#opexecutor)
- [Quads](#quads)
- [Mixed Graph Implementation Datasets](#mixed-datasets)
Re: CMS diff: ARQ - Extending Query Execution
Posted by "A. Soroka" <aj...@virginia.edu>.
Corrected, thanks!
---
A. Soroka
The University of Virginia Library
> On Jan 17, 2017, at 10:38 AM, Kim Ahlstrøm <an...@apache.org> wrote:
>
> Clone URL (Committers only):
> https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Farq-query-eval.mdtext
>
> Kim Ahlstrøm
>
> Index: trunk/content/documentation/query/arq-query-eval.mdtext
> ===================================================================
> --- trunk/content/documentation/query/arq-query-eval.mdtext (revision 1655891)
> +++ trunk/content/documentation/query/arq-query-eval.mdtext (working copy)
> @@ -3,7 +3,7 @@
> This page describes the mechanisms that can be used to extend and
> modify query execution within ARQ. Through these mechanisms, ARQ
> can be used to query different graph implementations and to provide
> -different query evaluation and opti-mization strategies for
> +different query evaluation and optimization strategies for
> particular circumstances. These mechanisms are used by
> [TDB-](../tdb) and [SDB](../sdb/).-
>
> @@ -19,12 +19,12 @@
> Jena itself can be extended by providing a new implementation of
> the `Graph` interface. This can be used to encapsulate specific
> specialised storage and also for wrapping non-RDF sources to look
> -like RDF. There is a common implementation framewo-fk provided-fby
> +like RDF. There is a common implementation framework provided by
> `GraphBase` so only one operation, the `find` method, needs to be
> 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
> -[basic graph matching](#stage-generator) or
> +[basic graph matching](#graph-matching-and-a-custom-stagegenerator) or
> [algebra level](#opexecutor).
>
> Applications writers who extend ARQ at the query execution level
> @@ -34,7 +34,7 @@
>
> - [Overview of ARQ Query processing-](#overview)
> - [The Main Query Engine](#main-query-engine)
> -- [Graph matching and a custom StageGenerator](#stage-generator)
> +- [Graph matching and a custom StageGenerator](#graph-matching-and-a-custom-stagegenerator)
> - [OpExecutor](#opexecutor)
> - [Quads](#quads)
> - [Mixed Graph Implementation Datasets](#mixed-datasets)
>