You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2015/07/26 12:50:20 UTC
svn commit: r959629 [6/10] - in /websites/staging/jena/trunk/content: ./
about_jena/ documentation/ documentation/assembler/ documentation/csv/
documentation/extras/ documentation/extras/querybuilder/
documentation/fuseki2/ documentation/hadoop/ docume...
Modified: websites/staging/jena/trunk/content/documentation/rdf/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/rdf/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/rdf/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/documentation/sdb/commands.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/commands.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/commands.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,9 +144,20 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB/Commands</h1>
- <p>This page describes the command line programs that can be used to
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This page describes the command line programs that can be used to
create an SDB store, load data into it and to issue queries.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li>
<p><a href="#scripts">Scripts</a></p>
@@ -173,11 +184,11 @@ create an SDB store, load data into it a
</ul>
</li>
</ul>
-<h2 id="scripts">Scripts</h2>
+<h2 id="scripts">Scripts<a class="headerlink" href="#scripts" title="Permanent link">¶</a></h2>
<p>The directory <code>bin/</code> contains shell scripts to run the commands
from the command line. The scripts are bash scripts which also run
over <a href="http://www.cygwin.com/" title="http://www.cygwin.com/">Cygwin</a>.</p>
-<h3 id="script-set-up">Script set up</h3>
+<h3 id="script-set-up">Script set up<a class="headerlink" href="#script-set-up" title="Permanent link">¶</a></h3>
<p>Set the environment variable <code>SDBROOT</code> to the root of the the SDB
installation.</p>
<p>A store description can include naming the class for the JDBC
@@ -205,7 +216,7 @@ Windows.</p>
<p>Alternatively, there are wrapper scripts in <code>$SDBROOT/bin2</code> which
can be placed in a convenient directory that is already on the
shell command path.</p>
-<h3 id="argument-structure">Argument Structure</h3>
+<h3 id="argument-structure">Argument Structure<a class="headerlink" href="#argument-structure" title="Permanent link">¶</a></h3>
<p>All commands take a SDB store description to extract the connection
and configuration information they need. This is written
<em><code>SPEC</code></em> in the command descriptions below but it can be
@@ -220,7 +231,7 @@ positional arguments.</p>
</pre></div>
-<h2 id="store-description">Store Description</h2>
+<h2 id="store-description">Store Description<a class="headerlink" href="#store-description" title="Permanent link">¶</a></h2>
<p>If this is not specified, commands load the description file
sdb.ttl from the current directory.</p>
<div class="codehilite"><pre> <span class="o">--</span><span class="n">sdb</span><span class="p">=</span><span class="o"><</span><span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span><span class="o">></span>
@@ -238,7 +249,7 @@ processed.</p>
<p>The directory <code>Store/</code> has example assembler files.</p>
<p>The full details of the assembler file is given in
'<a href="store_description.html" title="SDB/Store Description">SDB/Store Description</a>'</p>
-<h3 id="modifying-the-store-description">Modifying the Store Description</h3>
+<h3 id="modifying-the-store-description">Modifying the Store Description<a class="headerlink" href="#modifying-the-store-description" title="Permanent link">¶</a></h3>
<p>The individual items of a store description can be overridden by
various command arguments. The description in the assembler file is
read, then any command line arguments used to modify the
@@ -264,7 +275,7 @@ modified description.</p>
<p>The better way to handle passwords is to use environment variables
SDB_USER and SDB_PASSWORD because then the user/password is not
stored in a visible way.</p>
-<h3 id="logging-and-monitoring">Logging and Monitoring</h3>
+<h3 id="logging-and-monitoring">Logging and Monitoring<a class="headerlink" href="#logging-and-monitoring" title="Permanent link">¶</a></h3>
<p>All commands take the following arguments (although they may do
nothing if they make no sense to the command).</p>
<div class="codehilite"><pre> <span class="o">-</span><span class="n">v</span>
@@ -288,14 +299,14 @@ significant proportion in short operatio
<p>to log SQL actions on the database connection (but not the prepared
statements used by the loader). Can be repeated on the command
line.</p>
-<h2 id="sdb-commands">SDB Commands</h2>
-<h3 id="database-creation">Database creation</h3>
+<h2 id="sdb-commands">SDB Commands<a class="headerlink" href="#sdb-commands" title="Permanent link">¶</a></h2>
+<h3 id="database-creation">Database creation<a class="headerlink" href="#database-creation" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> <span class="n">sdbconfig</span> <span class="n">SPEC</span> <span class="p">[</span><span class="o">--</span><span class="n">create</span><span class="o">|--</span><span class="n">format</span><span class="o">|--</span><span class="n">indexes</span><span class="o">|--</span><span class="n">dropIndexes</span><span class="p">]</span>
</pre></div>
<p>Setup a database.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Option</th>
@@ -328,7 +339,7 @@ then building the query indexes with thi
<p>Truncate the store. Non-transactional. Destroys data.</p>
-<h3 id="loading-data">Loading data</h3>
+<h3 id="loading-data">Loading data<a class="headerlink" href="#loading-data" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> <span class="n">sdbload</span> <span class="n">SPEC</span> <span class="n">FILE</span> <span class="p">[</span><span class="n">FILE</span> <span class="p">...]</span>
</pre></div>
@@ -342,7 +353,7 @@ transaction.</p>
</pre></div>
-<h3 id="query">Query</h3>
+<h3 id="query">Query<a class="headerlink" href="#query" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> <span class="n">sdbquery</span> <span class="n">SPEC</span> <span class="o">--</span><span class="n">query</span><span class="p">=</span><span class="n">FILE</span>
</pre></div>
@@ -355,7 +366,7 @@ transaction.</p>
<p>Print details of a query. <code>X</code> is any of <code>query</code>, <code>op</code>, <code>sqlNode</code>,
<code>sql</code> or <code>plan</code>. <code>--print=X</code> can be repeated. --sql is short for
--print=sql. The default is <code>--print=sql</code>.</p>
-<h3 id="testing">Testing</h3>
+<h3 id="testing">Testing<a class="headerlink" href="#testing" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> <span class="n">sdbtest</span> <span class="n">SPEC</span> <span class="n">MANIFEST</span>
</pre></div>
@@ -363,7 +374,7 @@ transaction.</p>
<p>Execute a test manifest file. The manifest of all query tests,
which will test connection and loading of data, is in
<code><em>SDBROOT</em>/testing/manifest-sdb.ttl</code>.</p>
-<h3 id="other">Other</h3>
+<h3 id="other">Other<a class="headerlink" href="#other" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> <span class="n">sdbdump</span> <span class="n">SPEC</span> <span class="o">--</span><span class="n">out</span><span class="p">=</span><span class="n">SYNTAX</span>
</pre></div>
Modified: websites/staging/jena/trunk/content/documentation/sdb/configuration.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/configuration.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/configuration.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,11 +144,22 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Configuration</h1>
- <p>This page describe the configuration options available. These are
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This page describe the configuration options available. These are
options for query processing, not for the database layout and
storage, which is controlled by
<a href="store_description.html" title="SDB/Store Description">store descriptions</a>.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#setting-options">Setting Options</a></li>
<li><a href="#current-options">Current Options</a><ul>
@@ -158,7 +169,7 @@ storage, which is controlled by
</ul>
</li>
</ul>
-<h2 id="setting-options">Setting Options</h2>
+<h2 id="setting-options">Setting Options<a class="headerlink" href="#setting-options" title="Permanent link">¶</a></h2>
<p>Options can be set globally, through out the JVM, or on a per query
execution basis. SDB uses the same mechanism as
<a href="http://jena.sf.net/ARQ" title="http://jena.sf.net/ARQ">ARQ</a>.</p>
@@ -186,8 +197,8 @@ are short for the constants of class <co
or setup happens. Creation of a query execution object does not
compile the query, which happens when the appropriate <code>.exec</code>
method is called.</p>
-<h2 id="current-options">Current Options</h2>
-<table>
+<h2 id="current-options">Current Options<a class="headerlink" href="#current-options" title="Permanent link">¶</a></h2>
+<table class="table">
<thead>
<tr>
<th>Symbol</th>
@@ -223,7 +234,7 @@ method is called.</p>
</tr>
</tbody>
</table>
-<h3 id="queries-over-all-named-graphs">Queries over all Named Graphs</h3>
+<h3 id="queries-over-all-named-graphs">Queries over all Named Graphs<a class="headerlink" href="#queries-over-all-named-graphs" title="Permanent link">¶</a></h3>
<p>All the named graphs can be treated as a single graph in two ways:
either set the SDB option above or use the URI that refers to RDF
merge of the named graphs (<code>urn:x-arq:UnionGraph</code>).</p>
@@ -241,7 +252,7 @@ only:</p>
<li><code><urn:x-arq:UnionGraph></code> â the union of all named graphs, even
when the option for named union queries is not set.</li>
</ul>
-<h3 id="streaming-over-jdbc">Streaming over JDBC</h3>
+<h3 id="streaming-over-jdbc">Streaming over JDBC<a class="headerlink" href="#streaming-over-jdbc" title="Permanent link">¶</a></h3>
<p>By default, SDB processes results from SQL statements in a
streaming fashion. It is important to close query execution
objects, especially if not consuming all the results, because that
@@ -260,7 +271,7 @@ may be restrictions imposed by the datab
for your database for details.</p>
<p>In addition, operations on the graph API can be made streaming by
also setting the Graph API to streaming.</p>
-<h3 id="annotated-sql">Annotated SQL</h3>
+<h3 id="annotated-sql">Annotated SQL<a class="headerlink" href="#annotated-sql" title="Permanent link">¶</a></h3>
<p>SQL generation can include SQL comments to show how SPARQL has been
turned into SQL. This option is <code>true</code> by default and always set
for the command <code>sdbprint</code>.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/database_layouts.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/database_layouts.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/database_layouts.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Database Layouts</h1>
- <p><a href="index.html" title="SDB">SDB</a> does not have a single database layout. This
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a href="index.html" title="SDB">SDB</a> does not have a single database layout. This
page is an informal overview of the two main types ("layout2/hash"
and "layout2/index").</p>
<p>In SDB one store is one RDF dataset is one SQL database.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/databases_supported.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/databases_supported.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/databases_supported.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Databases Supported</h1>
- <table>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<table class="table">
<thead>
<tr>
<th>Product</th>
Modified: websites/staging/jena/trunk/content/documentation/sdb/dataset_description.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/dataset_description.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/dataset_description.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/documentation/sdb/db_notes.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/db_notes.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/db_notes.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,31 +144,42 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Database Notes</h1>
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="#db2">DB2</a></li>
<li><a href="#derby">Derby</a></li>
<li><a href="#ms-sql">MS SQL</a></li>
<li><a href="#mysql">MySQL</a></li>
<li><a href="#postgresql">PostgresQL</a></li>
</ul>
-<h2 id="db2">DB2</h2>
-<h3 id="database-creation">Database creation</h3>
+<h2 id="db2">DB2<a class="headerlink" href="#db2" title="Permanent link">¶</a></h2>
+<h3 id="database-creation">Database creation<a class="headerlink" href="#database-creation" title="Permanent link">¶</a></h3>
<p>The database should be created with code set UTF-8 so unicode is
enabled (SDB creates tables CCSID UNICODE for full
internationalization support).</p>
-<h2 id="derby">Derby</h2>
-<h3 id="loading-restriction">Loading Restriction</h3>
+<h2 id="derby">Derby<a class="headerlink" href="#derby" title="Permanent link">¶</a></h2>
+<h3 id="loading-restriction">Loading Restriction<a class="headerlink" href="#loading-restriction" title="Permanent link">¶</a></h3>
<p>Only one load operation can be active at any one time. Limitations
on temporary tables in Derby mean the the loader tables are not
temporary and hence are shared by all connections.</p>
-<h2 id="ms-sql">MS SQL</h2>
+<h2 id="ms-sql">MS SQL<a class="headerlink" href="#ms-sql" title="Permanent link">¶</a></h2>
<p>The collation sequence for the database must be one that is binary
(BIN in the name). It does not matter which one is used. Without
BIN, string matching is case insensitive but RDF requires case
sensitive literals and IRIs. The normal layout is not affected by
this because it does not use string comparisons.</p>
-<h2 id="mysql">MySQL</h2>
-<h3 id="national-characters">National Characters</h3>
+<h2 id="mysql">MySQL<a class="headerlink" href="#mysql" title="Permanent link">¶</a></h2>
+<h3 id="national-characters">National Characters<a class="headerlink" href="#national-characters" title="Permanent link">¶</a></h3>
<p>SDB formats all table columns used for storing text in the MySQL
schema to UTF-8. However, this does not cause the data to be
transmitted in UTF-8 over the JDBC connection.</p>
@@ -188,10 +199,10 @@ file.</p>
</pre></div>
-<h3 id="connection-timeouts">Connection timeouts</h3>
+<h3 id="connection-timeouts">Connection timeouts<a class="headerlink" href="#connection-timeouts" title="Permanent link">¶</a></h3>
<p>If you get the connection timing out after (by default) 8 hours of
no activity, try setting <code>autoReconnect=true</code> in the JDBC URL.</p>
-<h3 id="tuning">Tuning</h3>
+<h3 id="tuning">Tuning<a class="headerlink" href="#tuning" title="Permanent link">¶</a></h3>
<ol>
<li>For InndoDB, the critical parameter is
<code>innodb_buffer_pool_size</code>. See the MySQL sample configuration files
@@ -199,7 +210,7 @@ no activity, try setting <code>autoRecon
<li>Using ANALYZE TABLE on the database tables can improve the
choices made by the MySQL optimizer.</li>
</ol>
-<h3 id="connection-timeout">Connection Timeout</h3>
+<h3 id="connection-timeout">Connection Timeout<a class="headerlink" href="#connection-timeout" title="Permanent link">¶</a></h3>
<p>MySQL closes the JDBC connection after a period of no use (8 hours
by default).</p>
<p>While deprecated my MySQL, <code>?autoReconnect=true</code> may help here.</p>
@@ -208,8 +219,8 @@ call on a regular basis just to keep the
<code>SELECT * { <http://example/junk> <http://example/junk> <http://example/junk> }</code>).</p>
<p>Some connection pool systems automatic compensate for this feature
of MySQL.</p>
-<h2 id="postgresql">PostgresQL</h2>
-<h3 id="databases-must-use-utf-8-encoding">Databases must use UTF-8 encoding</h3>
+<h2 id="postgresql">PostgresQL<a class="headerlink" href="#postgresql" title="Permanent link">¶</a></h2>
+<h3 id="databases-must-use-utf-8-encoding">Databases must use UTF-8 encoding<a class="headerlink" href="#databases-must-use-utf-8-encoding" title="Permanent link">¶</a></h3>
<p>Create SDB stores with encoding UTF-8.</p>
<p>International character sets can cause corrupted databases
otherwise. The database will not pass the SDB test suite.</p>
@@ -222,7 +233,7 @@ command line, for example:</p>
</pre></div>
-<h3 id="improving-loading-rates">Improving loading rates</h3>
+<h3 id="improving-loading-rates">Improving loading rates<a class="headerlink" href="#improving-loading-rates" title="Permanent link">¶</a></h3>
<p>The index layout ("layout2/index") usually loads faster than the
hash form.</p>
<p><em>Existing store</em></p>
@@ -297,7 +308,7 @@ representative of the data.</p>
<p>Run <code>ANALYZE</code> on the database again.</p>
</li>
</ul>
-<h3 id="tuning_1">Tuning</h3>
+<h3 id="tuning_1">Tuning<a class="headerlink" href="#tuning_1" title="Permanent link">¶</a></h3>
<p>It is essential to run the PostgreSQL ANALYZE command on a
database, either during or after building. This is done via the
command line <code>psql</code> or via <code>pgAdmin</code>. The PostgreSQL documentation
Modified: websites/staging/jena/trunk/content/documentation/sdb/faq.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/faq.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/faq.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,11 +144,22 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB FAQ</h1>
- <h2 id="tune-your-database">Tune your database</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="tune-your-database">Tune your database<a class="headerlink" href="#tune-your-database" title="Permanent link">¶</a></h2>
<p>Database performance depends on the database being tuned. Some
databases default to "developer setup" which does not use much of
the RAM but is only for functional testing.</p>
-<h2 id="improving-loading-rates">Improving loading rates</h2>
+<h2 id="improving-loading-rates">Improving loading rates<a class="headerlink" href="#improving-loading-rates" title="Permanent link">¶</a></h2>
<p>For a large bulk load into an existing store, dropping the indexes,
doing the load and then recreating the indexes can be noticeably
faster.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/fuseki_integration.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/fuseki_integration.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/fuseki_integration.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/documentation/sdb/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB - persistent triple stores using relational databases</h1>
- <p>SDB uses an SQL database for the storage and query of RDF data.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>SDB uses an SQL database for the storage and query of RDF data.
Many databases are supported, both Open Source and proprietary.</p>
<p>An SDB store can be accessed and managed with the provided command
line scripts and via the Jena API.</p>
@@ -157,7 +168,7 @@ Use of SDB for new applications is not r
<p><i>This component is "maintenance only".</i></p>
<p><i><a href="../tdb/index.html">TDB</a> is faster, more scalable and better supported
than SDB.</i></p>
-<h2 id="status">Status</h2>
+<h2 id="status">Status<a class="headerlink" href="#status" title="Permanent link">¶</a></h2>
<p>As of June 2013 the Jena developers agreed to treat SDB as
being only maintanined where possible.
See <a href="http://mail-archives.apache.org/mod_mbox/jena-users/201306.mbox/%3c51B1A7FB.4070601@apache.org%3e">Future of SDB</a> thread on the mailing list.</p>
@@ -168,7 +179,7 @@ use it within their organizations.</p>
community come forward to develop it. The Jena team strongly recommends
the use of <a href="../tdb/">TDB</a> instead of SDB for all new development due to
TDBs substantially better performance and scalability.</p>
-<h2 id="documentation">Documentation</h2>
+<h2 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h2>
<ul>
<li><a href="installation.html">SDB Installation</a></li>
<li><a href="quickstart.html">Quickstart</a></li>
@@ -182,18 +193,18 @@ TDBs substantially better performance an
<li><a href="fuseki_integration.html">Fuseki Integration</a></li>
<li><a href="databases_supported.html">Databases supported</a></li>
</ul>
-<h2 id="downloads">Downloads</h2>
+<h2 id="downloads">Downloads<a class="headerlink" href="#downloads" title="Permanent link">¶</a></h2>
<p>SDB is distributed from the Apache Jena project. See the
<a href="/download/index.cgi">downloads page</a> for details.</p>
-<h2 id="support">Support</h2>
+<h2 id="support">Support<a class="headerlink" href="#support" title="Permanent link">¶</a></h2>
<p><a href="/help_and_support">Support and questions</a></p>
-<h2 id="details">Details</h2>
+<h2 id="details">Details<a class="headerlink" href="#details" title="Permanent link">¶</a></h2>
<ul>
<li><a href="loading_data.html">Loading data</a></li>
<li><a href="loading_performance.html">Loading performance</a></li>
<li><a href="query_performance.html">Query performance</a></li>
</ul>
-<h2 id="database-notes">Database Notes</h2>
+<h2 id="database-notes">Database Notes<a class="headerlink" href="#database-notes" title="Permanent link">¶</a></h2>
<p>List of <a href="databases_supported.html">databases supported</a></p>
<p>Notes:</p>
<ul>
Modified: websites/staging/jena/trunk/content/documentation/sdb/installation.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/installation.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/installation.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Installation</h1>
- <p>A
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>A
<a href="databases_supported.html" title="SDB/Databases Supported">suitable database</a>
must be installed separately. Any database installation should be
tuned according to the database documentation.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/javaapi.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/javaapi.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/javaapi.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,9 +144,20 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB JavaAPI</h1>
- <p>This page describes how to use SDB from Java.</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This page describes how to use SDB from Java.</p>
<p>Code examples are in <code>src-examples/</code> in the SDB distribution.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#concepts">Concepts</a></li>
<li><a href="#obtaining-the-store">Obtaining the Store</a><ul>
@@ -161,7 +172,7 @@
<li><a href="#executing-queries">Executing Queries</a></li>
<li><a href="#using-the-jena-model-api-with-sdb">Using the Jena Model API with SDB</a></li>
</ul>
-<h2 id="concepts">Concepts</h2>
+<h2 id="concepts">Concepts<a class="headerlink" href="#concepts" title="Permanent link">¶</a></h2>
<ul>
<li><code>Store</code></li>
<li><code>SDBFactory</code></li>
@@ -194,13 +205,13 @@ queries being sent to SDB.</p>
Java API and an SDB store, either to the default graph or one of
the named graphs. The <code>SDBFactory</code> can also create Jena Models
backed by such a graph.</p>
-<h2 id="obtaining-the-store">Obtaining the Store</h2>
+<h2 id="obtaining-the-store">Obtaining the Store<a class="headerlink" href="#obtaining-the-store" title="Permanent link">¶</a></h2>
<p>A store is build from a description. This can be a description in
file as a
<a href="../assembler">Jena assembler</a>
or the application can build the store description
programmatically.</p>
-<h3 id="from-a-configuration-file">From a configuration file</h3>
+<h3 id="from-a-configuration-file">From a configuration file<a class="headerlink" href="#from-a-configuration-file" title="Permanent link">¶</a></h3>
<p>The stored description is the only point where the specific details
of store are given. This includes connection information, the
database name, and database type. It makes sense to place this
@@ -236,7 +247,7 @@ store type.</p>
<p>See the full details of
<a href="store_description.html" title="SDB/Store Description">store description files</a>
for the options.</p>
-<h3 id="in-java-code">In Java code</h3>
+<h3 id="in-java-code">In Java code<a class="headerlink" href="#in-java-code" title="Permanent link">¶</a></h3>
<p>The less flexible way to create a store description is to build it
in Java. For example:</p>
<div class="codehilite"><pre> <span class="n">StoreDesc</span> <span class="n">storeDesc</span> <span class="p">=</span> <span class="n">new</span> <span class="n">StoreDesc</span><span class="p">(</span><span class="n">LayoutType</span><span class="p">.</span><span class="n">LayoutTripleNodesHash</span><span class="p">,</span>
@@ -248,7 +259,7 @@ in Java. For example:</p>
</pre></div>
-<h3 id="database-user-and-password">Database User and Password</h3>
+<h3 id="database-user-and-password">Database User and Password<a class="headerlink" href="#database-user-and-password" title="Permanent link">¶</a></h3>
<p>The user and password for the database can be set in explicitly in
the description file but it is usually better to use an environment
variable or Java system property because this avoid writing use and
@@ -257,7 +268,7 @@ password in a file.</p>
Java property: <code>jena.db.user</code></p>
<p>Environment variable: <code>SDB_PASSWORD</code>
Java property: <code>jena.db.password</code></p>
-<h2 id="connection-management">Connection Management</h2>
+<h2 id="connection-management">Connection Management<a class="headerlink" href="#connection-management" title="Permanent link">¶</a></h2>
<p>Each store has a JDBC connection associated with it.</p>
<p>In situations where such connections are managed externally, the
store object can be created and used within a single operation.</p>
@@ -296,7 +307,7 @@ container:</p>
</pre></div>
-<h2 id="formatting-or-emptying-the-store">Formatting or Emptying the Store</h2>
+<h2 id="formatting-or-emptying-the-store">Formatting or Emptying the Store<a class="headerlink" href="#formatting-or-emptying-the-store" title="Permanent link">¶</a></h2>
<p>SDB stores do not ensure that the database is formatted. You can
check whether the store is already formatted using:</p>
<div class="codehilite"><pre><span class="n">StoreUtils</span><span class="p">.</span><span class="n">isFormatted</span><span class="p">(</span><span class="n">store</span><span class="p">);</span>
@@ -316,12 +327,12 @@ full SDB store.</p>
</pre></div>
-<h2 id="loading-data">Loading data</h2>
+<h2 id="loading-data">Loading data<a class="headerlink" href="#loading-data" title="Permanent link">¶</a></h2>
<p>Data loading uses the standard Jena <code>Model.read</code> operations.
<code>GraphSDB</code>, and models made from a <code>GraphSDB</code>, implement the
standard Jena bulk data interface with backed by an SBD
implementation of that interface.</p>
-<h2 id="executing-queries">Executing Queries</h2>
+<h2 id="executing-queries">Executing Queries<a class="headerlink" href="#executing-queries" title="Permanent link">¶</a></h2>
<p>The interface to making queries with SDB is same as that for
<a href="../query/app_api.html">querying with ARQ</a>.
SDB is an ARQ query engine that can handle queries made on an RDF
@@ -354,7 +365,7 @@ associated with the particular implement
<p>If models or graphs backed by SDB are placed in a general Dataset
then the query is not efficiently executed by SDB.</p>
-<h2 id="using-the-jena-model-api-with-sdb">Using the Jena Model API with SDB</h2>
+<h2 id="using-the-jena-model-api-with-sdb">Using the Jena Model API with SDB<a class="headerlink" href="#using-the-jena-model-api-with-sdb" title="Permanent link">¶</a></h2>
<p>A Jena model can be connected to one graph in the store and used
with all the Jena API operations.</p>
<p>Here, the graph for the model is the the default graph:</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/loading_data.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/loading_data.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/loading_data.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Loading data</h1>
- <p>There are three ways to load data into SDB:</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>There are three ways to load data into SDB:</p>
<ol>
<li>Use the command utility
<a href="commands.html#Loading_data" title="SDB/Commands">sdbload</a></li>
@@ -153,7 +164,7 @@
</ol>
<p>The last one of these requires the application to signal the
beginning and end of batches.</p>
-<h2 id="loading-with-modelread">Loading with <code>Model.read</code></h2>
+<h2 id="loading-with-modelread">Loading with <code>Model.read</code><a class="headerlink" href="#loading-with-modelread" title="Permanent link">¶</a></h2>
<p>A Jena Model obtained from SDB via:</p>
<div class="codehilite"><pre><span class="n">SDBFactory</span><span class="p">.</span><span class="n">connectModel</span><span class="p">(</span><span class="n">store</span><span class="p">)</span>
</pre></div>
@@ -161,7 +172,7 @@ beginning and end of batches.</p>
<p>will automatically bulk load data for each call of one of the
<code>Model.read</code> operations.</p>
-<h2 id="loading-with-modeladd">Loading with <code>Model.add</code></h2>
+<h2 id="loading-with-modeladd">Loading with <code>Model.add</code><a class="headerlink" href="#loading-with-modeladd" title="Permanent link">¶</a></h2>
<p>The <code>Model.add</code> operations, in any form or combination of forms,
whether loading a single statement, list of statements, or another
model, will invoke the bulk loader if previously notified before an
@@ -189,7 +200,7 @@ add operation.</p>
additions to sizes appropriate to the underlying database. The bulk
loader is threaded with double-buffered; loading to the database
happens in parallel to the application thread and any RDF parsing.</p>
-<h2 id="how-the-loader-works">How the loader works</h2>
+<h2 id="how-the-loader-works">How the loader works<a class="headerlink" href="#how-the-loader-works" title="Permanent link">¶</a></h2>
<p>Loading consists of two phases: in the java VM, and on the database
itself. The SDB loader takes incoming triples and breaks them down
into components ready for the database. These prepared triples are
@@ -234,7 +245,7 @@ we are out of triples, the following hap
database handles almost all of the work uninterrupted (duplicate
suppression, hash to index lookup), which makes loading reasonably
quick.</p>
-<h2 id="duplicate-suppression">Duplicate Suppression</h2>
+<h2 id="duplicate-suppression">Duplicate Suppression<a class="headerlink" href="#duplicate-suppression" title="Permanent link">¶</a></h2>
<p>MySQL has a very useful <code>INSERT IGNORE</code>, which will keep going,
skipping an offending row if a uniqueness constraint is violated.
For other databases we need something else.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/loading_performance.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/loading_performance.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/loading_performance.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Loading performance</h1>
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="#introduction">Introduction</a></li>
<li><a href="#the-databases-and-hardware">The Databases and Hardware</a><ul>
<li><a href="#hardware">Hardware</a></li>
@@ -161,7 +172,7 @@
<li><a href="#results">Results</a></li>
<li><a href="#uniprot-700m-loading-tuning-helps">Uniprot 700m loading: Tuning Helps</a></li>
</ul>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">¶</a></h2>
<p>Performance reporting is an area prone to misinterpretation, and
such reports should be liberally decorated with disclaimers. In our
case there are an alarming number of variables: the hardware, the
@@ -179,37 +190,37 @@ sufficient:</p>
<p>We suggest that you don't choose your database based on these
figures. The performance is broadly similar, so if you already have
a relational database installed this is your best option.</p>
-<h2 id="the-databases-and-hardware">The Databases and Hardware</h2>
+<h2 id="the-databases-and-hardware">The Databases and Hardware<a class="headerlink" href="#the-databases-and-hardware" title="Permanent link">¶</a></h2>
<p>SDB supports a range of databases, but the figures here are limited
to SQLServer and Postgresql. The hardware used was identical,
although running linux (for Postgresql) and windows (for
SQLServer).</p>
-<h3 id="hardware">Hardware</h3>
+<h3 id="hardware">Hardware<a class="headerlink" href="#hardware" title="Permanent link">¶</a></h3>
<ul>
<li>Dual AMD Opteron processors, 64 bit, 1.8 GHz.</li>
<li>8 GB memory.</li>
<li>80 GB disk for database.</li>
</ul>
-<h3 id="windows-setup">Windows setup</h3>
+<h3 id="windows-setup">Windows setup<a class="headerlink" href="#windows-setup" title="Permanent link">¶</a></h3>
<ul>
<li>Windows server 2003</li>
<li>Java 6 64 bit</li>
<li>SQLServer 2005</li>
</ul>
-<h3 id="linux-setup">Linux setup</h3>
+<h3 id="linux-setup">Linux setup<a class="headerlink" href="#linux-setup" title="Permanent link">¶</a></h3>
<ul>
<li>Redhat Enterprise Linux 4</li>
<li>Java 6 64 bit</li>
<li>Postgresql 8.2</li>
</ul>
-<h2 id="the-dataset-and-queries">The Dataset and Queries</h2>
+<h2 id="the-dataset-and-queries">The Dataset and Queries<a class="headerlink" href="#the-dataset-and-queries" title="Permanent link">¶</a></h2>
<p>We use the Lehigh University Benchmark
<a href="http://swat.cse.lehigh.edu/projects/lubm/" title="http://swat.cse.lehigh.edu/projects/lubm/">http://swat.cse.lehigh.edu/projects/lubm/</a>
and dbpedia
<a href="http://dbpedia.org/" title="http://dbpedia.org/">http://dbpedia.org/</a>,
together with some example queries that each provides. You can find
the queries in SDB/PerfTests.</p>
-<h3 id="lubm">LUBM</h3>
+<h3 id="lubm">LUBM<a class="headerlink" href="#lubm" title="Permanent link">¶</a></h3>
<p>LUBM generates artifical datasets. To be useful one needs to apply
reasoning, and this was done in advance of loading. The queries are
quite stressful for SDB in that they are not very ground (in many
@@ -219,19 +230,19 @@ queries.</p>
<ul>
<li>Size: 19 million triples (including inferred triples).</li>
</ul>
-<h3 id="dbpedia">dbpedia</h3>
+<h3 id="dbpedia">dbpedia<a class="headerlink" href="#dbpedia" title="Permanent link">¶</a></h3>
<p>The dbpedia queries are, unlike LUBM, quite ground. dbpedia
contains many large literals, in contrast to LUBM.</p>
<ul>
<li>Size: 25 million triples.</li>
</ul>
-<h2 id="loading">Loading</h2>
+<h2 id="loading">Loading<a class="headerlink" href="#loading" title="Permanent link">¶</a></h2>
<p>All operations were performed using SDB's command line tools. The
data was loaded into a freshly formatted SDB store -- although
postgresql needs an ANALYSE to avoid silly planning -- then the
additional indexes were added.</p>
-<h2 id="results">Results</h2>
-<table>
+<h2 id="results">Results<a class="headerlink" href="#results" title="Permanent link">¶</a></h2>
+<table class="table">
<thead>
<tr>
<th>Benchmark</th>
@@ -291,7 +302,7 @@ additional indexes were added.</p>
</tr>
</tbody>
</table>
-<h2 id="uniprot-700m-loading-tuning-helps">Uniprot 700m loading: Tuning Helps</h2>
+<h2 id="uniprot-700m-loading-tuning-helps">Uniprot 700m loading: Tuning Helps<a class="headerlink" href="#uniprot-700m-loading-tuning-helps" title="Permanent link">¶</a></h2>
<p>To illustrate the variability in loading speed, and emphasise the
importance of tuning, consider the case of Uniprot
<a href="http://dev.isb-sib.ch/projects/uniprot-rdf/" title="http://dev.isb-sib.ch/projects/uniprot-rdf/">http://dev.isb-sib.ch/projects/uniprot-rdf/</a>.
Modified: websites/staging/jena/trunk/content/documentation/sdb/query_performance.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/query_performance.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/query_performance.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Query performance</h1>
- <p>This page compares the effect of SDB with RDB, Jena's usual
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This page compares the effect of SDB with RDB, Jena's usual
database layout. RDB was designed for supporting the fine-grained
API calls as well as having some support for basic graph patterns.
Therefore, the RDB design goals were not those of SDB.</p>
@@ -160,14 +171,14 @@ guide. The shape of the data, the hardwa
database, and it's configuration (particularly amount of memory
used), as well as the queries themselves all greatly contribute to
the execution costs.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#setup">Setup</a></li>
<li><a href="#lubm-query-1">LUBM Query 1</a></li>
<li><a href="#lubm-query-2">LUBM Query 2</a></li>
<li><a href="#summary">Summary</a></li>
</ul>
-<h2 id="setup">Setup</h2>
+<h2 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent link">¶</a></h2>
<p><a href="loading_performance.html#the-databases-and-hardware" title="SDB/Loading performance">Database and hardware setup</a>
was the same as for the
<a href="loading_performance.html" title="SDB/Loading performance">load performance</a>
@@ -177,7 +188,7 @@ tests.</p>
million triples. This data is larger than the database could
completely cache.</p>
<p>The queries are taken the LUBM suite and rewritten in SPARQL.</p>
-<h2 id="lubm-query-1">LUBM Query 1</h2>
+<h2 id="lubm-query-1">LUBM Query 1<a class="headerlink" href="#lubm-query-1" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre> <span class="n">PREFIX</span> <span class="n">rdf</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">w3</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>1999<span class="o">/</span>02<span class="o">/</span>22<span class="o">-</span><span class="n">rdf</span><span class="o">-</span><span class="n">syntax</span><span class="o">-</span><span class="n">ns</span>#<span class="o">></span>
<span class="n">PREFIX</span> <span class="n">ub</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">lehigh</span><span class="p">.</span><span class="n">edu</span><span class="o">/~</span><span class="n">zhp2</span><span class="o">/</span>2004<span class="o">/</span>0401<span class="o">/</span><span class="n">univ</span><span class="o">-</span><span class="n">bench</span><span class="p">.</span><span class="n">owl</span>#<span class="o">></span>
<span class="n">SELECT</span> <span class="o">*</span> <span class="n">WHERE</span>
@@ -191,7 +202,7 @@ completely cache.</p>
<p>Jena: 24.16s <br />
SDB/index: 0.014s<br />
SDB/hash: 0.04s</p>
-<h2 id="lubm-query-2">LUBM Query 2</h2>
+<h2 id="lubm-query-2">LUBM Query 2<a class="headerlink" href="#lubm-query-2" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre> <span class="n">PREFIX</span> <span class="n">rdf</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">w3</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>1999<span class="o">/</span>02<span class="o">/</span>22<span class="o">-</span><span class="n">rdf</span><span class="o">-</span><span class="n">syntax</span><span class="o">-</span><span class="n">ns</span>#<span class="o">></span>
<span class="n">PREFIX</span> <span class="n">ub</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">lehigh</span><span class="p">.</span><span class="n">edu</span><span class="o">/~</span><span class="n">zhp2</span><span class="o">/</span>2004<span class="o">/</span>0401<span class="o">/</span><span class="n">univ</span><span class="o">-</span><span class="n">bench</span><span class="p">.</span><span class="n">owl</span>#<span class="o">></span>
<span class="n">SELECT</span> <span class="o">*</span> <span class="n">WHERE</span>
@@ -212,7 +223,7 @@ specific starting point.</p>
SDB/index: 12.7s <br />
SDB/hash: 3.7s</p>
<p><strong>Notes:</strong> Removing the <code>rdf:type</code> statements actually slows the query down.</p>
-<h2 id="summary">Summary</h2>
+<h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">¶</a></h2>
<p>In SPARQL queries, there is often a sufficiently complex graph
pattern that the SDb design tradeoff provides significant
advantages in query performance.</p>
Modified: websites/staging/jena/trunk/content/documentation/sdb/quickstart.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/quickstart.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/quickstart.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,12 +144,23 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Quickstart</h1>
- <p>SDB provides some command line tools to work with SDB triple
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>SDB provides some command line tools to work with SDB triple
stores. In the following it assumed that you have a store
description set up for your database (<code>sdb.ttl</code>). See the
<a href="store_description.html" title="SDB/Store Description">store description format</a>
for details. The <code>Store/</code> directory for some examples.</p>
-<h3 id="setting-up-your-environment">Setting up your environment</h3>
+<h3 id="setting-up-your-environment">Setting up your environment<a class="headerlink" href="#setting-up-your-environment" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>$ <span class="n">export</span> <span class="n">SDBROOT</span><span class="p">=</span><span class="o">/</span><span class="n">path</span><span class="o">/</span><span class="n">to</span><span class="o">/</span><span class="n">sdb</span>
$ <span class="n">export</span> <span class="n">PATH</span><span class="p">=</span>$<span class="n">SDBROOT</span><span class="o">/</span><span class="n">bin</span><span class="p">:</span>$<span class="n">PATH</span>
$ <span class="n">export</span> <span class="n">SDB_USER</span><span class="p">=</span><span class="n">YourDatabaseUserName</span>
@@ -158,7 +169,7 @@ $ <span class="n">export</span> <span cl
</pre></div>
-<h3 id="initialising-the-database">Initialising the database</h3>
+<h3 id="initialising-the-database">Initialising the database<a class="headerlink" href="#initialising-the-database" title="Permanent link">¶</a></h3>
<p>Be aware that this will wipe existing data from the database.</p>
<div class="codehilite"><pre> $ <span class="n">sdbconfig</span> <span class="o">--</span><span class="n">sdb</span> <span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span> <span class="o">--</span><span class="n">format</span>
</pre></div>
@@ -166,21 +177,21 @@ $ <span class="n">export</span> <span cl
<p>This creates a basic layout. It does <em>not</em> add all indexes to the
triple table, which may be left until after loading.</p>
-<h3 id="loading-data">Loading data</h3>
+<h3 id="loading-data">Loading data<a class="headerlink" href="#loading-data" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> $ <span class="n">sdbload</span> <span class="o">--</span><span class="n">sdb</span> <span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span> <span class="n">file</span><span class="p">.</span><span class="n">rdf</span>
</pre></div>
<p>You might want to add the <code>--verbose</code> flag to show the load as it
progresses.</p>
-<h3 id="adding-indexes">Adding indexes</h3>
+<h3 id="adding-indexes">Adding indexes<a class="headerlink" href="#adding-indexes" title="Permanent link">¶</a></h3>
<p>You need to do this at some point if you want your queries to
execute in a reasonable time.</p>
<div class="codehilite"><pre> $ <span class="n">sdbconfig</span> <span class="o">--</span><span class="n">sdb</span> <span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span> <span class="o">--</span><span class="n">index</span>
</pre></div>
-<h3 id="query">Query</h3>
+<h3 id="query">Query<a class="headerlink" href="#query" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre> $ <span class="n">sdbquery</span> <span class="o">--</span><span class="n">sdb</span> <span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span> <span class="s">'SELECT * WHERE { ?s a ?p }'</span>
$ <span class="n">sdbquery</span> <span class="o">--</span><span class="n">sdb</span> <span class="n">sdb</span><span class="p">.</span><span class="n">ttl</span> <span class="o">--</span><span class="n">file</span> <span class="n">query</span><span class="p">.</span><span class="n">rq</span>
Modified: websites/staging/jena/trunk/content/documentation/sdb/store_description.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/store_description.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/store_description.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">SDB Store Description</h1>
- <p>Use of an SDB store requires a <code>Store</code> object which is described in
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Use of an SDB store requires a <code>Store</code> object which is described in
two parts:</p>
<ul>
<li>a connection to the database</li>
@@ -156,7 +167,7 @@ description.</p>
<p>Store objects themselves are lightweight so connections to an SDB
database can be created on a per-request basis as required for use
in J2EE application servers.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#store-descriptions">Store Descriptions</a></li>
<li><a href="#sdb-connections">SDB Connections</a></li>
@@ -167,7 +178,7 @@ in J2EE application servers.</p>
</ul>
</li>
</ul>
-<h2 id="store-descriptions">Store Descriptions</h2>
+<h2 id="store-descriptions">Store Descriptions<a class="headerlink" href="#store-descriptions" title="Permanent link">¶</a></h2>
<p>A store description identifies which storage layout is being used,
the connection to use and the database type.</p>
<div class="codehilite"><pre> <span class="p">[]</span> <span class="n">rdf</span><span class="p">:</span><span class="n">type</span> <span class="n">sdb</span><span class="p">:</span><span class="n">Store</span>Â <span class="p">;</span>
@@ -178,13 +189,13 @@ the connection to use and the database t
</pre></div>
-<h2 id="sdb-connections">SDB Connections</h2>
+<h2 id="sdb-connections">SDB Connections<a class="headerlink" href="#sdb-connections" title="Permanent link">¶</a></h2>
<p>SDB connections, objects of class <code>SDBConnection</code>, abstract away
from the details of the connection and also provide consist logging
and transaction operations. Currently, SDB connections encapsulate
JDBC connections but other connection technologies, such as direct
database APIs, can be added.</p>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<p>The <code>sdbType</code> is needed for both a connection and for a store
description. It can be given in either part of the complete store
description. If it is specified in both places, it must be the
@@ -209,8 +220,8 @@ same.</p>
<p>Examples of assembler files are to be found in the <code>Store/</code>
directory in the distribution.</p>
-<h2 id="vocabulary">Vocabulary</h2>
-<h3 id="store">Store</h3>
+<h2 id="vocabulary">Vocabulary<a class="headerlink" href="#vocabulary" title="Permanent link">¶</a></h2>
+<h3 id="store">Store<a class="headerlink" href="#store" title="Permanent link">¶</a></h3>
<p>The value of <code>sdbType</code> needed for the connection also applies to
choosing the store type.</p>
<p><code>layout</code>
@@ -221,7 +232,7 @@ choosing the store type.</p>
description.</p>
<p><code>engine</code>
~ Set the MySQL engine type (MySQL only).</p>
-<h3 id="connection">Connection</h3>
+<h3 id="connection">Connection<a class="headerlink" href="#connection" title="Permanent link">¶</a></h3>
<dl>
<dt><code>sdbType</code></dt>
<dd>The type of the database (e.g. "oracle", "MSSQLServerExpress",
Modified: websites/staging/jena/trunk/content/documentation/security/assembler.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/security/assembler.html (original)
+++ websites/staging/jena/trunk/content/documentation/security/assembler.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena Security - Assembler For a Secured Model</h1>
- <p>Jena Security provides a standard Jena assembler making it easy to use the <code>SecuredModel</code> in an Assembler based environment. To use the security assembler the assembler file must contain the lines:</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Jena Security provides a standard Jena assembler making it easy to use the <code>SecuredModel</code> in an Assembler based environment. To use the security assembler the assembler file must contain the lines:</p>
<div class="codehilite"><pre><span class="p">[]</span> <span class="n">ja</span><span class="p">:</span><span class="n">loadClass</span> "<span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">security</span><span class="p">.</span><span class="n">SecuredAssembler</span>" <span class="p">.</span>
<span class="nb">sec</span><span class="p">:</span><span class="n">Model</span> <span class="n">rdfs</span><span class="p">:</span><span class="n">subClassOf</span> <span class="n">ja</span><span class="p">:</span><span class="n">NamedModel</span> <span class="p">.</span>
</pre></div>
Modified: websites/staging/jena/trunk/content/documentation/security/evaluator.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/security/evaluator.html (original)
+++ websites/staging/jena/trunk/content/documentation/security/evaluator.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,17 +144,28 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena Security - SecurityEvaluator implementation</h1>
- <h2 id="overview">Overview</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h2>
<p>The SecurityEvaluator interface defines the access control operations. It provides the interface between the
authentication (answers the question: "who are you?") and the authorization (answers the question: "what can you
do?"), as such it provides access to the current principal (user). The javadocs contain detailed
requirements for implementations of the SecurityEvaluator interface, short notes are provided below.</p>
<p><strong>NOTE</strong> The security system caches intermediate results and will only call the evaluator if the answer is not
already in the cache. There is little or advantage to implementing caching in the SecurityEvaluator itself.</p>
-<h3 id="actions">Actions</h3>
+<h3 id="actions">Actions<a class="headerlink" href="#actions" title="Permanent link">¶</a></h3>
<p>Principals may perform Create, Read, Action or Delete operations on
secured resources. These operations are defined in the <code>Action</code> enum in the SecurtyEvaluator interface.</p>
-<h3 id="secnode">SecNode</h3>
+<h3 id="secnode">SecNode<a class="headerlink" href="#secnode" title="Permanent link">¶</a></h3>
<p>The security node is a class that tracks the type and node value. SecNodes are one of the four enumerated Types
found in the SecNodes class:</p>
<ul>
@@ -169,13 +180,13 @@ found in the SecNodes class:</p>
<li><code>SecNode.VARIABLE = new SecNode(Type.Any, "variable")</code> Indicates a variable in the triple.</li>
<li><code>SecNode.FUTURE = new SecNode(Type.Anonymous, "")</code> This is an anonymous node that will be created in the future.</li>
</ul>
-<h3 id="sectriple">SecTriple</h3>
+<h3 id="sectriple">SecTriple<a class="headerlink" href="#sectriple" title="Permanent link">¶</a></h3>
<p>The security triple is a class that provides a triple of SecNode objects. SecTriple also defines a single static
triple:</p>
<ul>
<li><code>SecTriple.ANY</code> = new SecTriple(SecNode.ANY, SeccNode.ANY, SecNode.ANY)` Matches any SecTriple.</li>
</ul>
-<h3 id="evaluator-methods">Evaluator Methods</h3>
+<h3 id="evaluator-methods">Evaluator Methods<a class="headerlink" href="#evaluator-methods" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">public</span> <span class="n">boolean</span> <span class="n">evaluate</span><span class="p">(</span> <span class="n">Object</span> <span class="n">principal</span><span class="p">,</span> <span class="n">Action</span> <span class="n">action</span><span class="p">,</span> <span class="n">SecNode</span> <span class="n">graphIRI</span> <span class="p">);</span>
</pre></div>
@@ -216,7 +227,7 @@ triple:</p>
<p>Returns the current principal or null if there is no current principal. </p>
-<h2 id="sample-implementation">Sample Implementation</h2>
+<h2 id="sample-implementation">Sample Implementation<a class="headerlink" href="#sample-implementation" title="Permanent link">¶</a></h2>
<p>This sample is for a graph that contains a set of messages, access to the messages are limited to
principals that the messages are to or from. Any triple that is not a message is not affected. This
implementation simply has a <code>setPrincipal(String name)</code> method. A real implementation would request the
Modified: websites/staging/jena/trunk/content/documentation/security/example.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/security/example.html (original)
+++ websites/staging/jena/trunk/content/documentation/security/example.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,10 +144,21 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Adding Jena-Security to Fuseki</h1>
- <h2 id="overview">Overview</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h2>
<p>The goal of this document is to add jena-security to a fuseki deployment to restrict access to graph data. This example will take the jena-security example application, deploy the data to a fuseki instance and add the jena-security to achieve the same access restrictions that the example application has.</p>
<p>To do this you will need a Fuseki installation, the Security Packages and a SecurityEvaluator implementation. For this example we will use the SecurityEvaluator from the Security-Examples.</p>
-<h2 id="set-up">Set up</h2>
+<h2 id="set-up">Set up<a class="headerlink" href="#set-up" title="Permanent link">¶</a></h2>
<p>This example uses Fuseki 2.0.0-SNAPSHOT, and Security 2.12.2-SNAPSHOT and Apache Commons Collections v4. If you are using an earlier Security version you will need to download the source code to compile the example.</p>
<p>Fuseki can be downloaded from:
[https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/]</p>
@@ -209,7 +220,7 @@ Uncompress the <code>commons-collections
<p>Run <code>fuseki-server âconfig=run/config.ttl</code> or <code>fuseki-server.bat âconfig=run/config.ttl</code></p>
</li>
</ol>
-<h2 id="review-of-configuration">Review of configuration</h2>
+<h2 id="review-of-configuration">Review of configuration<a class="headerlink" href="#review-of-configuration" title="Permanent link">¶</a></h2>
<p>At this point the system is configured with the following logins:</p>
<table>
<tr><th>Login</th><th>password</th><th>Access to</th></tr>
Modified: websites/staging/jena/trunk/content/documentation/security/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/security/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/security/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,10 +144,21 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena Security - A Security (Permissions) wrapper around Jena RDF implementation</h1>
- <p>JenaSecurity is a SecurityEvaluator interface and a set of dynamic proxies that apply that interface to Jena Graphs,
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>JenaSecurity is a SecurityEvaluator interface and a set of dynamic proxies that apply that interface to Jena Graphs,
Models, and associated methods and classes. It does not implement any specific security policy but provides a
framework for developers or integrators to implement any desired policy.</p>
-<h2 id="documentation">Documentation</h2>
+<h2 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h2>
<ul>
<li><a href="index.html#overview">Overview</a></li>
<li><a href="index.html#usage-notes">Usage Notes</a></li>
@@ -156,7 +167,7 @@ framework for developers or integrators
<li><a href="assembler.html">Assembler</a></li>
<li><a href="example.html">Adding Jena-Security to Fuseki</a></li>
</ul>
-<h2 id="overview">Overview</h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h2>
<p>Jena-security transparently intercepts calls to the Graph or Model interface, evaluates access restrictions and
either allows or rejects the access. The system is authentication agnostic and will work with most authentication
systems. The system uses dynamic proxies to wrap any Graph or Model implementation.
@@ -169,7 +180,7 @@ optionally triples within the graphs. </
<p>The javadocs have additional annotations that specify what permissions at graph and triple levels are required for
the user to execute the method.</p>
<p>There is an example jar that contains configuration examples for both a stand alone application and a fuseki configuration option.</p>
-<h2 id="usage-notes">Usage Notes</h2>
+<h2 id="usage-notes">Usage Notes<a class="headerlink" href="#usage-notes" title="Permanent link">¶</a></h2>
<p>When the system is correctly configured the developer creates a SecuredGraph by calling
<code>Factory.getInstance( SecurityEvaluator, String, Graph );</code>. Once created the resulting graph automatically
makes the appropriate calls to the SecurityEvaluator before passing any approved requests to the underlying graph.</p>
Modified: websites/staging/jena/trunk/content/documentation/serving_data/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/serving_data/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/serving_data/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>