Author: buildbot
Date: Thu Jan 17 18:12:03 2019
New Revision: 1039136
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb2/tdb2_cmds.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 17 18:12:03 2019
@@ -1 +1 @@
-1849996
+1851563
Modified: websites/staging/jena/trunk/content/documentation/tdb2/tdb2_cmds.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb2/tdb2_cmds.html
(original)
+++ websites/staging/jena/trunk/content/documentation/tdb2/tdb2_cmds.html Thu
Jan 17 18:12:03 2019
@@ -182,10 +182,20 @@ h2:hover > .headerlink, h3:hover > .head
</pre></div>
+<p>To load the data into a named graph, use the <code>--graph=IRI</code>
argument:</p>
+<div class="codehilite"><pre><span class="n">tdb2</span><span
class="p">.</span><span class="n">tdbloader</span> <span
class="o">--</span><span class="n">loc</span> <span class="n">DB</span> <span
class="o">--</span><span class="n">graph</span><span class="p">=</span><span
class="n">https</span><span class="p">:</span><span class="o">//</span><span
class="n">example</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">graph</span>#<span class="n">name</span>
<span class="n">file1</span>
+</pre></div>
+
+
+<p>For the complete syntax and list of all arguments use
<code>--help</code>:</p>
+<div class="codehilite"><pre><span class="n">tdb2</span><span
class="p">.</span><span class="n">tdbloader</span> <span
class="o">--</span><span class="n">help</span>
+</pre></div>
+
+
<p>All TDB2 loaders can update datasets and do not have to work on an empty
dataset. However, only the basic and sequential loader are fully
-transactional in the presense of crashes. The other loadrs, while
-faster, work by manipulting the low-level datastructures, and are tuned
+transactional in the presence of crashes. The other loaders, while
+faster, work by manipulating the low-level datastructures, and are tuned
for large changes of data. They do not provide perfect transaction
isolation in case a load goes wrong for some reason. The multiphase
loading operations use partial transactions which can leave the database
@@ -193,7 +203,7 @@ in a strange state.</p>
<p>When working with large data to load, it is advisable to check it
completely first with <code>riot --validate</code>. Parse errors during
loading can
lead to inconsistent indexing. Fixing bad data, even if legal RDF, such
-as bad lexicial forms of literals or bad URIs, is much easier before the
+as bad lexical forms of literals or bad URIs, is much easier before the
data is in the database.</p>
<p>Because loading in hardware dependent, the right choice for any
situation can only be found by trying each loader to see what works best
@@ -206,11 +216,11 @@ memory and not use CPU improves the load
<p>The basic loader loads data as a single transaction into the dataset on
a single thread. It is suitable for small data and also for
incrementally adding to a dataset safely, A machine crash while running
-this loader will not invaldiate the database; the load simply will not
happen.</p>
+this loader will not invalidate the database; the load simply will not
happen.</p>
<p><code>--loader=sequential</code></p>
<p>The sequential loader is a single threaded loader that loads the primary
index then each of the other indexes. It is suitable only for low resource
-hardware, especiallyin a low I/O bandwidth siuation.</p>
+hardware, especially in a low I/O bandwidth situation.</p>
<p><code>--loader=phased</code> (default)</p>
<p>The phased loader, the default if no <code>--loader</code> argument is
provided,
is balance between performance and hardware demands.</p>
