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 1834eaefb Updated site from main
(b1b3217aacc60ee6425868d5537b9d74dd845c0f)
1834eaefb is described below
commit 1834eaefbdc6d88b3a4dddd4ba34b5dcb8567d6e
Author: jenkins <[email protected]>
AuthorDate: Tue Jan 3 10:25:56 2023 +0000
Updated site from main (b1b3217aacc60ee6425868d5537b9d74dd845c0f)
---
.../fuseki2/fuseki-server-protocol.html | 7 -----
content/documentation/io/rdf-input.html | 30 ++--------------------
content/sitemap.xml | 4 +--
3 files changed, 4 insertions(+), 37 deletions(-)
diff --git a/content/documentation/fuseki2/fuseki-server-protocol.html
b/content/documentation/fuseki2/fuseki-server-protocol.html
index 535c4aa2e..54c1aaf2c 100644
--- a/content/documentation/fuseki2/fuseki-server-protocol.html
+++ b/content/documentation/fuseki2/fuseki-server-protocol.html
@@ -433,13 +433,6 @@ See <a href="fuseki-server-info.html">Fuseki Server
Information</a> for details
useful for managing the files externally.</p>
<p>The returned JSON object will have the form <code>{ backups: [ ... ]
}</code> where the <code>[]</code> array is
a list of file names.</p>
-<p>Since 4.7.0 backups are written to a temporary file in the same directory
and renamed on completion.
-In case of server crash, it will not be renamed.
-This guarantees backups are complete.
-Cleanup of incomplete backups can be done by users on application / container
start: remove all incomplete files.g</p>
-<h3 id="backup-policies">Backup policies</h3>
-<p>Users can use the backup api <a
href="/documentation/fuseki2/fuseki-server-protocol.html#backup">the Fuseki
HTTP Administration Protocol</a> to build backup policies.
-See issue for more information <a
href="https://github.com/apache/jena/issues/1500";>https://github.com/apache/jena/issues/1500</a>
.</p>
<h3 id="compact">Compact</h3>
<p>Pattern: <code>/$/compact/{name}</code></p>
<p>This operations initiates a database compaction task and returns a JSON
object with the task Id in it.</p>
diff --git a/content/documentation/io/rdf-input.html
b/content/documentation/io/rdf-input.html
index a0176db05..c18d03324 100644
--- a/content/documentation/io/rdf-input.html
+++ b/content/documentation/io/rdf-input.html
@@ -460,41 +460,15 @@ this is useful when you don’t want to go to the
trouble of writing a full
logic in normal iterator style.</p>
<p>To do this you use <code>AsyncParser.asyncParseTriples</code> which parses
the input on
another thread:</p>
-<pre><code> IteratorCloseable<Triple> iter =
AsyncParser.asyncParseTriples(filename);
+<pre><code> Iterator<Triple> iter =
AsyncParser.asyncParseTriples(filename);
iter.forEachRemaining(triple->{
// Do something with triple
});
</code></pre>
-<p>Calling the iterator’s close method stops parsing and closes the
involved resources.
-For N-Triples and N-Quads, you can use
+<p>For N-Triples and N-Quads, you can use
<code>RiotParsers.createIteratorNTriples(input)</code> which parses the input
on the
calling thread.</p>
<p><a
href="https://github.com/apache/jena/blob/main/jena-examples/src/main/java/arq/examples/riot/ExRIOT9_AsyncParser.java";>RIOT
example 9</a>.</p>
-<p>Additional control over parsing is provided by the
<code>AsyncParser.of(...)</code> methods which return
<code>AsyncParserBuilder</code> instances.
-The builder features a fluent API that allows for fine-tuning internal buffer
sizes as well as eventually obtaining
-a standard Java <code>Stream</code>. Calling the stream’s close method
stops parsing and closes the involved resources.
-Therefore, these streams are best used in conjunction with try-with-resources
blocks:</p>
-<pre><code> try (Stream<Triple> stream = AsyncParser.of(filename)
- .setQueueSize(2).setChunkSize(100).streamTriples().limit(1000)) {
- // Do something with the stream
- }
-</code></pre>
-<p>The AsyncParser also supports parsing RDF into a stream of
<code>EltStreamRDF</code> elements. Each element can hold a triple, quad,
prefix, base IRI or exception.
-For all <code>Stream</code>-based methods there also exist
<code>Iterator</code>-based versions:</p>
-<pre><code> IteratorCloseable<EltStreamRDF> it =
AsyncParser.of(filename).asyncParseElements();
- try {
- while (it.hasNext()) {
- EltStreamRDF elt = it.next();
- if (elt.isTriple()) {
- // Do something with elt.getTriple();
- } else if (elt.isPrefix()) {
- // Do something with elt.getPrefix() and elt.getIri();
- }
- }
- } finally {
- Iter.close(it);
- }
-</code></pre>
<h3 id="filter-the-output-of-parsing">Filter the output of parsing</h3>
<p>When working with very large files, it can be useful to
process the stream of triples or quads produced
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 9b1610739..652ffd822 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -409,7 +409,7 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/fuseki-server-protocol.html</loc>
- <lastmod>2022-09-13T12:11:16+03:00</lastmod>
+ <lastmod>2022-07-27T16:28:14+02:00</lastmod>
</url>
<url>
@@ -714,7 +714,7 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdf-input.html</loc>
- <lastmod>2022-08-24T16:11:32+02:00</lastmod>
+ <lastmod>2022-08-26T15:49:37+01:00</lastmod>
</url>
<url>
