Author: buildbot
Date: Mon Sep 1 07:59:30 2014
New Revision: 920895
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb/faqs.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 1 07:59:30 2014
@@ -1 +1 @@
-1620878
+1621697
Modified: websites/staging/jena/trunk/content/documentation/tdb/faqs.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb/faqs.html (original)
+++ websites/staging/jena/trunk/content/documentation/tdb/faqs.html Mon Sep 1
07:59:30 2014
@@ -184,15 +184,19 @@ applications portable to another SPARQL
<p><a name="impossibly-large-object"></a></p>
<h2 id="what-is-the-impossibly-large-object-exception">What is the
<em>Impossibly Large Object</em> exception?</h2>
<p>The <em>Impossibly Large Object</em> exception is an exception that occurs
when part of your TDB dataset has become corrupted. It may
-only affect a small section of your dataset so may only occur intermittently
depending on your queries. A query that touches
-the entirety of the dataset will always experience this exception e.g.</p>
+only affect a small section of your dataset so may only occur intermittently
depending on your queries. For example some queries
+may continue to function normally while other queries or queries with/without
particular features may fail. A particular query that
+fails with this error should continue to always fail unless the database is
modified.</p>
+<p>A query that touches the entirety of the dataset will always encounter this
exception and can be used to verify whether your
+database has this problem e.g.</p>
<div class="codehilite"><pre><span class="n">SELECT</span> <span
class="o">*</span> <span class="n">WHERE</span> <span class="p">{</span> <span
class="p">{</span> ?<span class="n">s</span> ?<span class="n">p</span> ?<span
class="n">o</span> <span class="p">}</span> <span class="n">UNION</span> <span
class="p">{</span> <span class="n">GRAPH</span> ?<span class="n">g</span> <span
class="p">{</span> ?<span class="n">s</span> ?<span class="n">p</span> ?<span
class="n">o</span> <span class="p">}</span> <span class="p">}</span> <span
class="p">}</span>
</pre></div>
-<p>The corruption may have happened at any time in the past and once it has
happened there
-is no way to repair it. Corrupted datasets will need to be rebuilt from the
original source data, 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>
+<p>The corruption may have happened at any time in the past and once it has
happened there is no way to repair it. Corrupted datasets
+will need to be rebuilt from the original source data, 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>
+<p>To resolve this problem you <strong>must</strong> rebuild your database
from the original source data, a corrupted database <strong>cannot</strong> be
repaired.</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>tdbloader</code> and <code>tdbloader2</code> differ in how they build
databases.</p>
@@ -211,7 +215,7 @@ the OS therefore it is important to not
out. What you should set the JVM heap to will depend on the kinds of queries
that you are running, very specific queries will not need a large heap whereas
queries that touch
large amounts of data or use operators that may require lots of data to be
buffered in-memory e.g. <code>DISTINCT</code>, <code>GROUP BY</code>,
<code>ORDER BY</code> may need a much larger heap depending
on the overall size of your database.</p>
-<p>There is no hard and fast guidance we can give you on the exact number
since it depends heavily on your data and your workload. Please ask on our
mailing lists
+<p>There is no hard and fast guidance we can give you on the exact numbers
since it depends heavily on your data and your workload. Please ask on our
mailing lists
(see our <a href="../help_and_support/">Ask</a> page) and provide as much
detail as possible about your data and workload if you would like us to attempt
to provide more specific guidance.</p>
<p><a name="fuseki-tdb-memory-leak"></a></p>
<h2 id="does-fusekitdb-have-a-memory-leak">Does Fuseki/TDB have a memory
leak?</h2>
