Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Farq-query-eval.mdtext
Haozhe 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) @@ -10,7 +10,7 @@ ARQ can be [extended in various ways](extension.html) to incorporate custom code into a query. [Custom filter functions](extension.html#value-functions) and -[property functions](extension.html#property-functio-ns) p-rovi-de ways +[property functions](extension.html#property-functio-ns) provide ways to add application specific code. The [free text search](/documentation/larq/) capabilities, using Apache Lucene, are provided via a property function. Custom filter @@ -19,7 +19,7 @@ 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. @@ -474,7 +474,7 @@ A custom query engine enables an extension to choose which datasets it wishes to handle. It also allows the extension to intercept query execution during the setup of the execution so it can modify -the algebra expression, introduce it's own algebra extensions, +the algebra expression, introduce its own algebra extensions, choose which high-level optimizations to apply and also transform to the expression into quad form. Execution can proceed with the normal algorithm or a custom `OpExecutor` or a custom Stage
