You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by gi...@apache.org on 2021/11/15 12:11:40 UTC

[jena-site] branch asf-staging updated: Staged site from xloader (fc011713d64e0790f19286c0f02a86df89100e13)

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/jena-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 22f1181  Staged site from xloader (fc011713d64e0790f19286c0f02a86df89100e13)
22f1181 is described below

commit 22f11815f7e9483c4faf3d3a2077f0bbfa85e108
Author: jenkins <bu...@apache.org>
AuthorDate: Mon Nov 15 12:11:38 2021 +0000

    Staged site from xloader (fc011713d64e0790f19286c0f02a86df89100e13)
---
 content/documentation/index.xml                 | 12 ++++-----
 content/documentation/query/arq-query-eval.html |  1 -
 content/documentation/sparql-apis/index.html    | 36 ++++++++++++++++++++-----
 content/documentation/tdb/commands.html         | 36 ++++++++++++++-----------
 content/documentation/tdb/faqs.html             | 16 +++++++++--
 content/documentation/tdb/tdb-xloader.html      | 18 ++++++++-----
 content/index.xml                               | 12 ++++-----
 content/sitemap.xml                             | 10 +++----
 8 files changed, 91 insertions(+), 50 deletions(-)

diff --git a/content/documentation/index.xml b/content/documentation/index.xml
index bc957ce..525bfea 100644
--- a/content/documentation/index.xml
+++ b/content/documentation/index.xml
@@ -182,7 +182,7 @@ Not currently supported:
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/sparql-apis/</guid>
-      <description>Jump to &amp;ldquo;Changes&amp;quot;.
+      <description>Jump to the &amp;ldquo;Changes&amp;rdquo; section.
 Overview The SPARQL specifications provide query, update and the graph store protocol (GSP).
 For working with RDF data:
    API GPI     Model Graph   Statement Triple   Resource Node   Literal Node   String Var   Dataset DatasetGraph    Quad    and for SPARQL,
@@ -1658,7 +1658,7 @@ Having the description in a file means that the data that the application is goi
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/tdb/commands.html</guid>
-      <description>Contents  Installation Scripts  Script set up - bash scripts Script set up - Windows batch files   Command line script arguments  Setting options from the command line   TDB Commands  Store description tdbloader tdbloader2 tdbquery tdbdump tdbstats    Installation From Apache Jena version 2.7.x onwards, TDB is now installed as part of a single integrated Jena package. There is no longer a need to install a separate TDB package to run the TDB command line tools, or to u [...]
+      <description>Contents  Installation Scripts  Script set up - bash scripts Script set up - Windows batch files   Command line script arguments  Setting options from the command line   TDB Commands  Store description tdbloader TDB xloader tdbquery tdbdump tdbstats    Installation From Apache Jena version 2.7.x onwards, TDB is now installed as part of a single integrated Jena package. There is no longer a need to install a separate TDB package to run the TDB command line tools, or to  [...]
     </item>
     
     <item>
@@ -1698,7 +1698,7 @@ SPARQL has the concept of a dataset description. In a query string, the clauses
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/tdb/faqs.html</guid>
-      <description>FAQs  Does TDB support Transactions? Can I share a TDB dataset between multiple applications? What is the Impossibly Large Object exception? What are the ObjectFile.read() and ObjectFileStorage.read() errors? What is the difference between tdbloader and tdbloader2? How large a Java heap size should I use for TDB? Does Fuseki/TDB have a memory leak? Should I use a SSD? Why do I get the exception Can&amp;rsquo;t open database at location /path/to/db as it is already lock [...]
+      <description>FAQs  What are TDB1 and TDB2? Does TDB support Transactions? Can I share a TDB dataset between multiple applications? What is the Impossibly Large Object exception? What are the ObjectFile.read() and ObjectFileStorage.read() errors? What is the difference between tdbloader and tdbloader2? How large a Java heap size should I use for TDB? Does Fuseki/TDB have a memory leak? Should I use a SSD? Why do I get the exception Can&amp;rsquo;t open database at location /path/to/ [...]
     </item>
     
     <item>
@@ -1795,9 +1795,9 @@ The file access mechanism can be set explicitly, but this is not a good idea for
       <guid>https://jena.apache.org/documentation/tdb/tdb-xloader.html</guid>
       <description>TDB xloader (&amp;ldquo;x&amp;rdquo; for external) is a bulkloader for very large datasets. The goal is stability and reliability for long running loading, running on modest and
 xloader is not a replacement for regular TDB1 and TDB2 loaders.
-&amp;ldquo;tdb1.xloader&amp;rdquo; was called &amp;ldquo;tdbloader2&amp;rdquo; and has some improvements.
-It is not as fast as other TDB loaders on dataset where the general loaders work on without encountering progressive slowdown.
-The xloaders for TDB1 and TDB2 are not identical.</description>
+Theer are two scripts to load data using the xlaoder subsystem.
+&amp;ldquo;tdb1.xloader&amp;rdquo;, which was called &amp;ldquo;tdbloader2&amp;rdquo; and has some improvements.
+It is not as fast as other TDB loaders on dataset where the general loaders work on without encountering progressive slowdown.</description>
     </item>
     
     <item>
diff --git a/content/documentation/query/arq-query-eval.html b/content/documentation/query/arq-query-eval.html
index ad345e0..9770cfa 100644
--- a/content/documentation/query/arq-query-eval.html
+++ b/content/documentation/query/arq-query-eval.html
@@ -557,7 +557,6 @@ custom query engine and overriding <code>QueryEngineMain.modifyOp</code>:</p>
 <pre><code>  @Override
   protected Op modifyOp(Op op)
   {
-     // Cope with initial bindings.
      op = Substitute.substitute(op, initialInput) ;
      // Use standard optimizations.
      op = super.modifyOp(op) ;
diff --git a/content/documentation/sparql-apis/index.html b/content/documentation/sparql-apis/index.html
index 05437af..698cb1b 100644
--- a/content/documentation/sparql-apis/index.html
+++ b/content/documentation/sparql-apis/index.html
@@ -171,7 +171,7 @@
             </div>
             <h1 class="title">Apache Jena SPARQL APIs</h1>
             
-	<p>Jump to &ldquo;<a href="#changes">Changes</a>&quot;.</p>
+	<p>Jump to the &ldquo;<a href="#changes">Changes</a>&rdquo; section.</p>
 <h2 id="overview">Overview</h2>
 <p>The SPARQL specifications provide
 <a href="https://www.w3.org/TR/sparql11-query/">query</a>,
@@ -301,12 +301,10 @@ necessary.</li>
 <p>Deprecate modifying <code>QueryExecution</code> after it is built.</p>
 </li>
 <li>
-<p>Parameterization for remote queries.
-Parameterization - replacing variables by values before sending
-a query - makes the query into a template. The same applies to updates.
-This is also provided uniformly for local queries and should be used in
-preference to the local-only &ldquo;initial binding&rdquo; approach which is
-similarly but not identical.</p>
+<p>Substitution of variables for concrete values in query and update execution.
+This is a form of paramterization that works in both local and remnote usage
+(unlike &ldquo;intial bindings&rdquo; which are only available for lcoal query execution).
+See the <a href="#substitution">substitution section</a> section below.</p>
 </li>
 <li>
 <p><code>HttpOp</code>, using <code>java.net.http.HttpClient</code>, is split into <code>HttpRDF</code> for
@@ -326,6 +324,30 @@ a dependency. Eventually, `HttpOp`` and dependecy on  Apache HttpClient will be
 <code>RDFLink</code> provide APIs.</p>
 </li>
 </ul>
+<h2 id="substitution">Substitution</h2>
+<p>All query and update builders provide operations to uses a query and substitute
+variables for concrete RDF terms in the execution</p>
+<p>Unlike &ldquo;initial bindings&rdquo; substitution is provided in query and update builders
+for both local and remote cases.</p>
+<p>Substitution is always &ldquo;replace variable with RDF term&rdquo; in a query or update
+that is correct syntax. This means is does not apply to <code>INSERT DATA</code> or <code>DELETE DATA</code> but can be used with <code>INSERT { ?s ?p ?o } WHERE {}</code> and
+<code>DELETE { ?s ?p ?o } WHERE {}</code>.</p>
+<p>Full example:
+<a href="https://github.com/afs/jena/tree/main/jena-arq/src-examples/arq/examples/ExQuerySubstitute_01.java">ExQuerySubstitute_01.java</a>.</p>
+<pre><code>    ResultSet resultSet1 = QueryExecution.dataset(dataset)
+            .query(prefixes+&quot;SELECT * { ?person foaf:name ?name }&quot;)
+            .substitution(&quot;name&quot;, name1)
+            .select();
+    ResultSetFormatter.out(resultSet1);
+</code></pre><p>Substitution is to be preferred over &ldquo;initial bindings&rdquo; because it is clearly
+defined and applies to both query and update in both local and remote uses.</p>
+<p>&ldquo;Substitution&rdquo; and &ldquo;initial bindings&rdquo; are similar but not identical.</p>
+<p>See also</p>
+<ul>
+<li><a href="documentation/query/parameterized-sparql-strings.html">Parameterized Queries</a></li>
+<li><a href="https://jena.apache.org/documentation/extras/querybuilder/index.html">Jena Query Builder</a></li>
+</ul>
+<p>which provide a different ways to build a query.</p>
 <h2 id="ttrdfconnectiontt"><tt>RDFConnection</tt></h2>
 <p><a href="../rdfconnection/">RDFConnection</a></p>
 <pre><code>    try ( RDFConnection conn = RDFConnectionRemote.service(dataURL).build()) {
diff --git a/content/documentation/tdb/commands.html b/content/documentation/tdb/commands.html
index c7249eb..caeb6e6 100644
--- a/content/documentation/tdb/commands.html
+++ b/content/documentation/tdb/commands.html
@@ -194,7 +194,7 @@
 <ul>
 <li><a href="#store-description">Store description</a></li>
 <li><a href="#tdbloader">tdbloader</a></li>
-<li><a href="#tdbloader2">tdbloader2</a></li>
+<li><a href="#tdb-xloader">TDB xloader</a></li>
 <li><a href="#tdbquery">tdbquery</a></li>
 <li><a href="#tdbdump">tdbdump</a></li>
 <li><a href="#tdbstats">tdbstats</a></li>
@@ -258,9 +258,26 @@ are loaded into the default graph, quad formats (e.g. N-Quads, TriG)
 are loaded into the dataset according to the name or the default graph.</p>
 <p>Bulk loader and index builder. Performs bulk load operations more
 efficiently than simply reading RDF into a TDB-back model.</p>
+<h3 id="tdbxloader">tdb.xloader</h3>
+<p><code>tdb1.xloader</code> and <code>tdb2.xloader</code> are bulk loaders for very large data for TDB1
+and TDB2.</p>
+<p>See <a href="./tdb-xloader.html">TDB xloader</a> for more information. These loaders only
+work on Linux and Mac OS/X since it relies on some Unix system utilities.</p>
+<h3 id="tdbquery"><code>tdbquery</code></h3>
+<p>Invoke a SPARQL query on a store. Use <code>--time</code> for timing
+information. The store is attached on each run of this command so
+timing includes some overhead not present in a running system.</p>
+<p>Details about query execution can be obtained &ndash; see notes on the
+<a href="optimizer.html#investigating-what-is-going-on">TDB Optimizer</a>.</p>
+<h3 id="tdbdump"><code>tdbdump</code></h3>
+<p>Dump the store in
+<a href="http://www.w3.org/TR/n-quads/">N-Quads</a>
+format.</p>
+<h3 id="tdbstats"><code>tdbstats</code></h3>
+<p>Produce a statistics for the dataset. See the
+<a href="optimizer.html#statistics-rule-file">TDB Optimizer description.</a>.</p>
 <h3 id="tdbloader2"><code>tdbloader2</code></h3>
-<p>Bulk loader and index builder. Faster than <code>tdbloader</code> but only works
-on Linux and Mac OS/X since it relies on some Unix system utilities.</p>
+<p><em>This has been replace by  <a href="./tdb-xloader.html">TDB xloader</a>.</em></p>
 <p>This bulk loader can only be used to create a database. It may
 overwrite existing data. It requires accepts the <code>--loc</code> argument and a
 list of files to load e.g.</p>
@@ -283,19 +300,6 @@ looks to be/is insufficient.</p>
 wish to have the <a href="http://www.ivarch.com/programs/pv.shtml">PipeViewer</a>
 tool installed on your system as this will provide extra progress information
 during the indexing phase of the build.</p>
-<h3 id="tdbquery"><code>tdbquery</code></h3>
-<p>Invoke a SPARQL query on a store. Use <code>--time</code> for timing
-information. The store is attached on each run of this command so
-timing includes some overhead not present in a running system.</p>
-<p>Details about query execution can be obtained &ndash; see notes on the
-<a href="optimizer.html#investigating-what-is-going-on">TDB Optimizer</a>.</p>
-<h3 id="tdbdump"><code>tdbdump</code></h3>
-<p>Dump the store in
-<a href="http://www.w3.org/TR/n-quads/">N-Quads</a>
-format.</p>
-<h3 id="tdbstats">tdbstats</h3>
-<p>Produce a statistics for the dataset. See the
-<a href="optimizer.html#statistics-rule-file">TDB Optimizer description.</a>.</p>
 
 
         </div>
diff --git a/content/documentation/tdb/faqs.html b/content/documentation/tdb/faqs.html
index 5afa3c7..11127d8 100644
--- a/content/documentation/tdb/faqs.html
+++ b/content/documentation/tdb/faqs.html
@@ -178,6 +178,7 @@
             
 	<h2 id="faqs">FAQs</h2>
 <ul>
+<li><a href="#tdv1-tdb2">What are TDB1 and TDB2?</a></li>
 <li><a href="#transactions">Does TDB support Transactions?</a></li>
 <li><a href="#multi-jvm">Can I share a TDB dataset between multiple applications?</a></li>
 <li><a href="#impossibly-large-object">What is the <em>Impossibly Large Object</em> exception?</a></li>
@@ -192,6 +193,12 @@
 <li><a href="#tdb2-lock">What is the <em>Unable to check TDB lock owner, the lock file contents appear to be for a TDB2 database. Please try loading this location as a TDB2 database</em> error?</a></li>
 <li><a href="#not-answered">My question isn&rsquo;t answered here?</a></li>
 </ul>
+<p>&lt;a name=&quot;tdb1-tdb2&gt;</a></p>
+<h2 id="tdb1-and-tdb2">TDB1 and TDB2</h2>
+<p>TDB2 is a later generation of database for Jena. It is more robust and can
+handle large update transactions.</p>
+<p>These are different databases systems - the have different on-disk file formats
+and databases for one are not compatible with other database engine.</p>
 <p><a name="transactions"></a></p>
 <h2 id="does-tdb-support-transactions">Does TDB support transactions?</h2>
 <p>Yes, TDB provides
@@ -206,10 +213,10 @@ transactionally.</p>
 <p><a name="multi-jvm"></a></p>
 <h2 id="can-i-share-a-tdb-dataset-between-multiple-applications">Can I share a TDB dataset between multiple applications?</h2>
 <p>Multiple applications, running in multiple JVMs, using the same
-file databases is <strong>not</strong> supported and has a high risk of data corruption.  Once corrupted a database cannot be repaired
+file databases is <strong>not</strong> supported and has a high risk of data corruption.  Once corrupted, a database cannot be repaired
 and must be rebuilt from the original source data. Therefore there <strong>must</strong> be a single JVM
 controlling the database directory and files.</p>
-<p>From 1.1.0 onwards TDB includes automatic prevention of multi-JVM usage which prevents this under most circumstances and helps
+<p>TDB includes automatic prevention of multi-JVM usage which prevents this under most circumstances and helps
 protect your data from corruption.</p>
 <p>If you wish to share a TDB dataset between applications use our <a href="../fuseki2/">Fuseki</a> component which provides a
 database server. Fuseki supports <a href="http://www.w3.org/TR/sparql11-query/">SPARQL Query</a>,
@@ -235,8 +242,13 @@ will need to be rebuilt from the original source data, this is why we <strong>st
 <p>As noted above to resolve this problem you <strong>must</strong> rebuild your database from the original source data, a corrupted database <strong>cannot</strong>
 be repaired. This is why we <strong>strongly</strong> recommend you use <a href="tdb_transactions.html">transactions</a> since this protects your dataset against
 corruption.</p>
+<h2 id="what-is-tdbxloader">What is <code>tdb.xloader</code>?</h2>
+<p><code>tdb1.xloader</code> and <code>tdb2.xloader</code> are bulk laodrs for very large dataset that
+take several hours to load.</p>
+<p>See <a href="./tdb-xloader.html">TDB xloader</a> for more information.</p>
 <p><a name="tdbloader-vs-tdbloader2"></a></p>
 <h2 id="what-is-the-different-between-tdbloader-and-tdbloader2">What is the different between <code>tdbloader</code> and <code>tdbloader2</code>?</h2>
+<p><code>tdbloader2</code> has been replaced by <code>tdb1.xloader</code> and <code>tdb2.xloader</code> for TDB1 and TDB2 respectively.</p>
 <p><code>tdbloader</code> and <code>tdbloader2</code> differ in how they build databases.</p>
 <p><code>tdbloader</code> is Java based and uses the same TDB APIs that you would use in your own Java code to perform the data load.  The advantage of this is that
 it supports incremental loading of data into a TDB database.  The downside is that the loader will be slower for initial database builds.</p>
diff --git a/content/documentation/tdb/tdb-xloader.html b/content/documentation/tdb/tdb-xloader.html
index c7ba640..dcb0a8b 100644
--- a/content/documentation/tdb/tdb-xloader.html
+++ b/content/documentation/tdb/tdb-xloader.html
@@ -179,13 +179,14 @@
 	<p>TDB xloader (&ldquo;x&rdquo; for external) is a bulkloader for very large datasets. The goal
 is stability and reliability for long running loading, running on modest and</p>
 <p>xloader is not a replacement for regular TDB1 and TDB2 loaders.</p>
-<p>&ldquo;tdb1.xloader&rdquo; was called &ldquo;tdbloader2&rdquo; and has some improvements.</p>
+<p>Theer are two scripts to load data using the xlaoder subsystem.</p>
+<p>&ldquo;tdb1.xloader&rdquo;, which was called &ldquo;tdbloader2&rdquo; and has some improvements.</p>
 <p>It is not as fast as other TDB loaders on dataset where the general loaders work
 on without encountering progressive slowdown.</p>
 <p>The xloaders for TDB1 and TDB2 are not identical. The TDB2 is more capable; it
 is based on the same design approach with further refinements to building the
 node table and to reduce the total amount of temporary file space used.</p>
-<p>The xloader does not run on MS Windows. It uses and external sort program from
+<p>The xloader does not run on MS Windows. It uses an external sort program from
 unix - <code>sort(1)</code>.</p>
 <p>The xloader only builds a fresh database from empty.
 It can not be used to load an existing database.</p>
@@ -193,16 +194,19 @@ It can not be used to load an existing database.</p>
 <p><code>tdb2.xloader --loc DIRECTORY</code> FILE&hellip;</p>
 <p>or</p>
 <p><code>tdb1.xloader --loc DIRECTORY</code> FILE&hellip;</p>
-<p>Additioally, there is an argument <code>--tmpdir</code> to use a different directory for
+<p>Additionally, there is an argument <code>--tmpdir</code> to use a different directory for
 temporary files.</p>
-<p><code>FILE</code> is any RDF syntax supported by Jena.</p>
+<p><code>FILE</code> is any RDF syntax supported by Jena. Syntax is detemined by file
+extension and can include an addtional &ldquo;.gz&rdquo; or &ldquo;.bz2&rdquo; for compresses files.</p>
 <h3 id="advice">Advice</h3>
-<p><code>xloader</code> uses a lot of temporary disk space.</p>
 <p>To avoid a load failing due to a syntax or other data error, it is advisable to
 run <code>riot --check</code> on the data first. Parsing is faster than loading.</p>
+<p>The TDB databases will tak eup a lot of disk space and in addition during
+loading <code>xloader</code> uses a significant amout of temporary disk space.</p>
 <p>If desired, the data can be converted to <a href="../io/rdf-binary.html">RDF Thrift</a> at
-this stage by adding <code>--stream rdf-thrift</code> to the riot checking run.
-Parsing RDF Thrift is faster than parsing N-Triples although the bulk of the loading process is not limited by parser speed.</p>
+this stage by adding <code>--stream rdf-thrift</code> to the riot checking run.  Parsing
+RDF Thrift is faster than parsing N-Triples although the bulk of the loading
+process is not limited by parser speed.</p>
 <p>Do not capture the bulk loader output in a file on the same disk as the database
 or temporary directory; it slows loading down.</p>
 
diff --git a/content/index.xml b/content/index.xml
index 82b9568..022cd5f 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -225,7 +225,7 @@ Not currently supported:
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/sparql-apis/</guid>
-      <description>Jump to &amp;ldquo;Changes&amp;quot;.
+      <description>Jump to the &amp;ldquo;Changes&amp;rdquo; section.
 Overview The SPARQL specifications provide query, update and the graph store protocol (GSP).
 For working with RDF data:
    API GPI     Model Graph   Statement Triple   Resource Node   Literal Node   String Var   Dataset DatasetGraph    Quad    and for SPARQL,
@@ -1931,7 +1931,7 @@ Having the description in a file means that the data that the application is goi
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/tdb/commands.html</guid>
-      <description>Contents  Installation Scripts  Script set up - bash scripts Script set up - Windows batch files   Command line script arguments  Setting options from the command line   TDB Commands  Store description tdbloader tdbloader2 tdbquery tdbdump tdbstats    Installation From Apache Jena version 2.7.x onwards, TDB is now installed as part of a single integrated Jena package. There is no longer a need to install a separate TDB package to run the TDB command line tools, or to u [...]
+      <description>Contents  Installation Scripts  Script set up - bash scripts Script set up - Windows batch files   Command line script arguments  Setting options from the command line   TDB Commands  Store description tdbloader TDB xloader tdbquery tdbdump tdbstats    Installation From Apache Jena version 2.7.x onwards, TDB is now installed as part of a single integrated Jena package. There is no longer a need to install a separate TDB package to run the TDB command line tools, or to  [...]
     </item>
     
     <item>
@@ -1971,7 +1971,7 @@ SPARQL has the concept of a dataset description. In a query string, the clauses
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://jena.apache.org/documentation/tdb/faqs.html</guid>
-      <description>FAQs  Does TDB support Transactions? Can I share a TDB dataset between multiple applications? What is the Impossibly Large Object exception? What are the ObjectFile.read() and ObjectFileStorage.read() errors? What is the difference between tdbloader and tdbloader2? How large a Java heap size should I use for TDB? Does Fuseki/TDB have a memory leak? Should I use a SSD? Why do I get the exception Can&amp;rsquo;t open database at location /path/to/db as it is already lock [...]
+      <description>FAQs  What are TDB1 and TDB2? Does TDB support Transactions? Can I share a TDB dataset between multiple applications? What is the Impossibly Large Object exception? What are the ObjectFile.read() and ObjectFileStorage.read() errors? What is the difference between tdbloader and tdbloader2? How large a Java heap size should I use for TDB? Does Fuseki/TDB have a memory leak? Should I use a SSD? Why do I get the exception Can&amp;rsquo;t open database at location /path/to/ [...]
     </item>
     
     <item>
@@ -2068,9 +2068,9 @@ The file access mechanism can be set explicitly, but this is not a good idea for
       <guid>https://jena.apache.org/documentation/tdb/tdb-xloader.html</guid>
       <description>TDB xloader (&amp;ldquo;x&amp;rdquo; for external) is a bulkloader for very large datasets. The goal is stability and reliability for long running loading, running on modest and
 xloader is not a replacement for regular TDB1 and TDB2 loaders.
-&amp;ldquo;tdb1.xloader&amp;rdquo; was called &amp;ldquo;tdbloader2&amp;rdquo; and has some improvements.
-It is not as fast as other TDB loaders on dataset where the general loaders work on without encountering progressive slowdown.
-The xloaders for TDB1 and TDB2 are not identical.</description>
+Theer are two scripts to load data using the xlaoder subsystem.
+&amp;ldquo;tdb1.xloader&amp;rdquo;, which was called &amp;ldquo;tdbloader2&amp;rdquo; and has some improvements.
+It is not as fast as other TDB loaders on dataset where the general loaders work on without encountering progressive slowdown.</description>
     </item>
     
     <item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 8b85b4d..2c3326c 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -109,7 +109,7 @@
   
   <url>
     <loc>https://jena.apache.org/documentation/sparql-apis/</loc>
-    <lastmod>2021-09-27T16:55:34+01:00</lastmod>
+    <lastmod>2021-11-15T12:00:22+00:00</lastmod>
   </url>
   
   <url>
@@ -164,7 +164,7 @@
   
   <url>
     <loc>https://jena.apache.org/documentation/query/arq-query-eval.html</loc>
-    <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+    <lastmod>2021-11-15T12:00:22+00:00</lastmod>
   </url>
   
   <url>
@@ -324,7 +324,7 @@
   
   <url>
     <loc>https://jena.apache.org/documentation.html</loc>
-    <lastmod>2021-11-12T12:33:33+00:00</lastmod>
+    <lastmod>2021-11-15T12:00:36+00:00</lastmod>
   </url>
   
   <url>
@@ -919,7 +919,7 @@
   
   <url>
     <loc>https://jena.apache.org/documentation/tdb/commands.html</loc>
-    <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+    <lastmod>2021-11-15T12:00:36+00:00</lastmod>
   </url>
   
   <url>
@@ -939,7 +939,7 @@
   
   <url>
     <loc>https://jena.apache.org/documentation/tdb/faqs.html</loc>
-    <lastmod>2020-06-26T14:59:03+01:00</lastmod>
+    <lastmod>2021-11-15T12:00:36+00:00</lastmod>
   </url>
   
   <url>