This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3afed96 Updated site from main
(9a03ac1f35b1a25d119ed176d7f656d3b1c1bd05)
3afed96 is described below
commit 3afed9671407402b1ae90d2cc2d54b250f8eea0f
Author: jenkins <[email protected]>
AuthorDate: Thu Feb 24 09:58:13 2022 +0000
Updated site from main (9a03ac1f35b1a25d119ed176d7f656d3b1c1bd05)
---
content/documentation/tdb/tdb_transactions.html | 6 +++---
content/sitemap.xml | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/documentation/tdb/tdb_transactions.html
b/content/documentation/tdb/tdb_transactions.html
index f94c2bf..31305d2 100644
--- a/content/documentation/tdb/tdb_transactions.html
+++ b/content/documentation/tdb/tdb_transactions.html
@@ -209,7 +209,7 @@ via a copy-on-write mechanism. Update transactions can be
of any size.</p>
<a
href="http://en.wikipedia.org/wiki/Write-ahead_logging";>write-ahead-logging</a>.
All
changes made inside a write-transaction are written to
<a href="http://en.wikipedia.org/wiki/Journaling_file_system";>journals</a>,
then propagated
-to the main database at a suitable moment. Transactions is TDB1 are limited in
+to the main database at a suitable moment. Transactions in TDB1 are limited in
size to a few 10’s of million triples because they retain data in-memory
until
indexes can be updated.</p>
<p>Transactional TDB supports one active write transaction, and
@@ -234,7 +234,7 @@ transactions, the highest
<li><a href="http://en.wikipedia.org/wiki/Nested_transaction";>Nested
transactions</a>
are not supported.</li>
</ul>
-<p>TDB2 remved the limitations of TDB1:</p>
+<p>TDB2 removed the limitations of TDB1:</p>
<ul>
<li>Some active transaction state is held exclusively in-memory,
limiting scalability.</li>
@@ -370,7 +370,7 @@ same storage. in both cases, the transactions are
independent.</p>
<p>Multiple applications, running in multiple JVMs, using the same
file databases is not 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. TDB includes automatic
prevention against multi-JVM
+controlling the database directory and files. TDB includes automatic
prevention against multi-JVM usage
which prevents this under most circumstances.</p>
<p>Use <a href="../fuseki2/">Fuseki</a> to provide a database server for
multiple
applications. Fuseki supports <a
href="http://www.w3.org/TR/sparql11-query/";>SPARQL
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 376a376..758c1bc 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -984,7 +984,7 @@
<url>
<loc>https://jena.apache.org/documentation/tdb/tdb_transactions.html</loc>
- <lastmod>2022-01-06T14:44:32+00:00</lastmod>
+ <lastmod>2022-02-23T13:13:57+00:00</lastmod>
</url>
<url>
