jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thom...@apache.org
Subject svn commit: r1793486 [2/6] - in /jackrabbit/site/live/oak/docs: ./ architecture/ coldstandby/ css/ features/ images/ js/ nodestore/ nodestore/document/ nodestore/segment/ oak-mongo-js/ oak_api/ plugins/ query/ security/ security/accesscontrol/ security...
Date Tue, 02 May 2017 13:04:23 GMT
Modified: jackrabbit/site/live/oak/docs/migration.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/migration.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/migration.html (original)
+++ jackrabbit/site/live/oak/docs/migration.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -248,7 +250,7 @@
 <p><tt>oak-upgrade</tt> module creates an executable jar file. It can be invoked like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar [options] source destination
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar [options] source destination
 </pre></div></div>
 <p>The <tt>source</tt> and <tt>destination</tt> are the node store paths/URIs. Following node stores are supported:</p>
 
@@ -273,7 +275,7 @@
 <p>Examples:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     path/to/the/repository \
     mongodb://localhost:27017/oak
 
@@ -287,7 +289,7 @@ java -jar oak-upgrade-*.jar \
 <p>In order to upgrade Jackrabbit 2 repository to the new node store, pass the path to the <tt>repository</tt> directory as the <tt>source</tt> parameter. Optionally, you may also pass the path to the <tt>repository.xml</tt> file as a separate parameter. Examples:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     path/to/the/jr2/repository \
     path/to/repository.xml \
     path/to/the/new/repository
@@ -420,7 +422,7 @@ java -jar oak-upgrade-*.jar \
 <p>Example:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     --copy-binaries \
     --src-datastore=/old/repository/datastore \
     --fileblobstore=/new/repository/datastore \
@@ -432,7 +434,7 @@ java -jar oak-upgrade-*.jar \
 <p>Using S3DataStore as a source or destination for binaries requires passing two arguments: <tt>s3datastore</tt> and <tt>s3config</tt>. The first one should point to the datastore directory (eg. <tt>crx-quickstart/repository/datastore</tt>). The second should be used to define the <tt>org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.cfg</tt> configuration file path. File should have following format:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">accessKey=...
+<div class="source"><pre class="prettyprint">accessKey=...
 secretKey=...
 s3Bucket=...
 s3Region=eu-west-1
@@ -452,7 +454,7 @@ maxErrorRetry=10
 <p>It&#x2019;s possible to define a list of content subtrees to include or exclude during the migration. By default, the whole repository gets copied. In order to copy only a subtree, use the <tt>--include-paths</tt>. For example, the following command will copy only the <tt>/content/site</tt> and <tt>/content/other_site</tt> subtrees:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     --include-paths=/content/site,/content/other_site \
     /old/repository \
     /new/repository
@@ -460,7 +462,7 @@ maxErrorRetry=10
 <p>You may also exclude specific paths from being copied. Following command will copy the whole content without the <tt>/content/redundant_site</tt>:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     --exclude-paths=/content/redundant_site \
     /old/repository \
     /new/repository
@@ -468,7 +470,7 @@ maxErrorRetry=10
 <p>By default, the source repository replaces the destination repository (if there&#x2019;s one). For instance, in the first example if the <tt>/content/site</tt> node already exists in the destination repository, it&#x2019;ll be removed and replaced by the source node. It&#x2019;s also possible to merge content from the source repository with <tt>--merge-paths</tt>:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-upgrade-*.jar \
+<div class="source"><pre class="prettyprint">java -jar oak-upgrade-*.jar \
     --include-paths=/content/site \
     --merge-paths=/content/site \
     /old/repository \
@@ -482,7 +484,7 @@ maxErrorRetry=10
 <p>There are two parameters: <tt>--copy-orphaned-versions</tt> and <tt>--copy-versions</tt>. Both accepts boolean values or a <tt>YYYY-MM-DD</tt> date. Examples:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums"># only copy referenced versions
+<div class="source"><pre class="prettyprint"># only copy referenced versions
 java -jar oak-upgrade-*.jar \
     --copy-orphaned-versions=false \
     /old/repository /new/repository
@@ -520,12 +522,12 @@ java -jar oak-upgrade-*.jar \
 <p>In order to do that, create a new Maven project, with appropriate implementation. Then create following file:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">src/main/resources/META-INF/services/org.apache.jackrabbit.oak.spi.commit.CommitHook
+<div class="source"><pre class="prettyprint">src/main/resources/META-INF/services/org.apache.jackrabbit.oak.spi.commit.CommitHook
 </pre></div></div>
 <p>The file should contain just one line - the name of the class with the <tt>CoomitHook</tt> implementation. Build the project and attach the JAR to the oak-upgrade class path:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -cp my-commit-hook.jar:oak-upgrade-*.jar org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade [normal oak-upgrade parameters]
+<div class="source"><pre class="prettyprint">java -cp my-commit-hook.jar:oak-upgrade-*.jar org.apache.jackrabbit.oak.upgrade.cli.OakUpgrade [normal oak-upgrade parameters]
 </pre></div></div>
 <p>A custom <tt>RepositoryInitializer</tt> can be injected in a similar way.</p></div>
 <div class="section">
@@ -544,7 +546,7 @@ java -jar oak-upgrade-*.jar \
 <p>In the second case oak-upgrade emits following warning and breaks:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">Checkpoints won't be copied, because no external datastore has been specified. This will result in the full repository reindexing on the first start. Use --skip-checkpoints to force the migration or see https://jackrabbit.apache.org/oak/docs/migration.html#Checkpoints_migration for more info.
+<div class="source"><pre class="prettyprint">Checkpoints won't be copied, because no external datastore has been specified. This will result in the full repository reindexing on the first start. Use --skip-checkpoints to force the migration or see https://jackrabbit.apache.org/oak/docs/migration.html#Checkpoints_migration for more info.
 </pre></div></div>
 <p>The easiest way to fix this issue is specifying the source datastore in the command line options (eg. <tt>--src-datastore</tt> or <tt>--src-s3datastore</tt>).</p>
 <p>The warning may also be ignored, but in this case the repository will be fully reindexed on the first startup. It may be a long process, especially for the big instance. Repository won&#x2019;t be usable until the reindexing process is done. Use <tt>--skip-checkpoints</tt> option to suppress the warning. </p></div></div>
@@ -575,7 +577,7 @@ java -jar oak-upgrade-*.jar \
 <p>Create a configuration for the <tt>org.apache.jackrabbit.oak.spi.blob.osgi.SplitBlobStoreService</tt>.</p>
   
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">split.old.blobstore.type=INTERNAL
+<div class="source"><pre class="prettyprint">split.old.blobstore.type=INTERNAL
 # optional:
 repository.home=crx-quickstart/repository
 </pre></div></div>
@@ -599,7 +601,7 @@ repository.home=crx-quickstart/repositor
 <p>Create a configuration for the <tt>org.apache.jackrabbit.oak.spi.blob.osgi.SplitBlobStoreService</tt>.</p>
   
 <div class="source">
-<div class="source"><pre class="prettyprint linenums"># use DOCUMENT or SEGMENT, depending on the NodeStore type:
+<div class="source"><pre class="prettyprint"># use DOCUMENT or SEGMENT, depending on the NodeStore type:
 split.old.blobstore.type=SEGMENT
 # optional:
 repository.home=crx-quickstart/repository

Modified: jackrabbit/site/live/oak/docs/nodestore/document/node-bundling.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/document/node-bundling.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/document/node-bundling.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/document/node-bundling.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -280,13 +282,13 @@
 <p>Bundling is enabled on per nodetype basis. Bundling definitions are defined as content in the repository under <tt>/jcr:system/rep:documentStore/bundlor</tt>.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+ &lt;node type name&gt;
+<div class="source"><pre class="prettyprint">+ &lt;node type name&gt;
   - pattern - multi 
 </pre></div></div>
 <p>For example below content structure enables bundling for nodes of type <tt>nt:file</tt> and <tt>app:Asset</tt></p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+ jcr:system
+<div class="source"><pre class="prettyprint">+ jcr:system
   + documentstore
     + bundlor
       + nt:file (oak:Unstructured)
@@ -346,7 +348,7 @@
 <p>Lets take an example of <tt>nt:file</tt> node like below</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+ /content/book.jpg 
+<div class="source"><pre class="prettyprint">+ /content/book.jpg 
   - jcr:createdBy = &quot;admin&quot;
   - jcr:primaryType = &quot;nt:file&quot;
   + jcr:content
@@ -360,7 +362,7 @@
 <p>This JCR node structure would be stored in MongoDB in 2 documents</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
        &quot;_id&quot;            : &quot;2:/content/book.jpg&quot;,
        &quot;jcr:created&quot;      : {&quot;r151ce899ac3-0-1&quot; : &quot;\&quot;dat:2015-12-23T16:41:43.055+05:30\&quot;&quot;},
        &quot;_modified&quot;        : NumberLong(1450869100),
@@ -389,7 +391,7 @@
 <p>Now with bundling pattern like</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+ jcr:system
+<div class="source"><pre class="prettyprint">+ jcr:system
   + documentstore
     + bundlor
       + nt:file (oak:Unstructured)
@@ -398,7 +400,7 @@
 <p>Would bundle the 2 nodes in nt:file node structure in same MongoDB Document</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
         &quot;_id&quot;                              : &quot;2:/content/book.jpg&quot;,
         &quot;jcr:primaryType&quot;                 : { &quot;r15866f15753-0-1&quot; : &quot;\&quot;nam:nt:file\&quot;&quot;},
         &quot;jcr:content/jcr:primaryType&quot;     : { &quot;r15866f15753-0-1&quot; : &quot;\&quot;nam:nt:resource\&quot;&quot;},
@@ -425,7 +427,7 @@
 <p>Lets take a more complex content structure. Assume a nodetype <tt>app:Asset</tt> having following content</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">/content/banner.png
+<div class="source"><pre class="prettyprint">/content/banner.png
   - jcr:primaryType = &quot;app:Asset&quot;
   + jcr:content
     - jcr:primaryType = &quot;app:AssetContent&quot;
@@ -457,7 +459,7 @@
 <p>Lets define a bundling pattern like below</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+ jcr:system
+<div class="source"><pre class="prettyprint">+ jcr:system
   + documentstore
     + bundlor
       + nt:file (oak:Unstructured)
@@ -468,7 +470,7 @@
 <p>With this bundling pattern same app:Asset structure would be stored in 1 MongoDB Document excluding &#x2018;comments&#x2019; and &#x2018;xmp&#x2019; nodes</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
 
   &quot;_children&quot;: true,
   &quot;_modified&quot;: 1469081925,

Modified: jackrabbit/site/live/oak/docs/nodestore/document/secondary-store.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/document/secondary-store.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/document/secondary-store.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/document/secondary-store.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -330,14 +332,14 @@
 <p>Create an OSGi config file <tt>org.apache.jackrabbit.oak.segment.SegmentNodeStoreFactory-secondary.config</tt> with following content</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">role=&quot;secondary&quot;
+<div class="source"><pre class="prettyprint">role=&quot;secondary&quot;
 </pre></div></div>
 <p>This would create a SegmentNodeStore in secondary role and uses default <tt>segmentstore-secondary</tt> directory to store the segment files. Refer to <a href="../../osgi_config.html#config-SegmentNodeStoreService">config options</a> for more details. Note all the options for <tt>SegmentNodeStoreService</tt> are applicable for <tt>SegmentNodeStoreFactory</tt></p>
 <p><b>2. Configure SecondaryStoreCacheService (optional)</b></p>
 <p>By default secondary NodeStore would be activated based on previous config only. However it can be tweaked further by creating an OSGi config file <tt>org.apache.jackrabbit.oak.plugins.document.secondary.SecondaryStoreCacheService.config</tt></p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">includedPaths=[ \
+<div class="source"><pre class="prettyprint">includedPaths=[ \
   &quot;/libs&quot;, \
   &quot;/apps&quot;, \
   &quot;/content&quot;

Modified: jackrabbit/site/live/oak/docs/nodestore/documentmk.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/documentmk.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/documentmk.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/documentmk.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -331,7 +333,7 @@
 <p>The repository data is stored in two collections: the <tt>nodes</tt> collection for node data, and the <tt>blobs</tt> collection for binaries. There is a third collection, <tt>clusterNodes</tt>, which contains metadata of all cluster nodes. The data can be viewed using the MongoDB shell:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&gt; show collections
+<div class="source"><pre class="prettyprint">&gt; show collections
 blobs
 clusterNodes
 nodes
@@ -342,7 +344,7 @@ nodes
 <p>The basic MongoDB document of a node in Oak looks like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_id&quot; : &quot;1:/node&quot;,
     &quot;_deleted&quot; : {
         &quot;r13f3875b5d1-0-1&quot; : &quot;false&quot;
@@ -369,7 +371,7 @@ nodes
 <p>Adding a property <tt>prop</tt> with value <tt>foo</tt> to the node in a next step will result in the following document:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13f3875b5d1-0-1&quot; : &quot;false&quot;
     },
@@ -392,7 +394,7 @@ nodes
 <p>After the node is deleted the document looks like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13f3875b5d1-0-1&quot; : &quot;false&quot;,
         &quot;r13f38835063-2-1&quot; : &quot;true&quot;
@@ -436,7 +438,7 @@ nodes
 <p>A root node may look like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13fcda88ac0-0-1&quot; : &quot;false&quot;,
     },
@@ -458,7 +460,7 @@ nodes
 <p>The root node was created in revision <tt>r13fcda88ac0-0-1</tt> and later in revision <tt>r13fcda91720-0-1</tt> property <tt>prop</tt> was set to <tt>foo</tt>. To keep the example simple, we now assume a branch is created based on the revision the root node was last modified and a branch commit is done to modify the existing property. After the branch commit the root node looks like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13fcda88ac0-0-1&quot; : &quot;false&quot;,
     },
@@ -483,7 +485,7 @@ nodes
 <p>When the branch is later merged, the root node will look like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13fcda88ac0-0-1&quot; : &quot;false&quot;,
     },
@@ -511,7 +513,7 @@ nodes
 <p>Over time the size of a document grows because DocumentMK adds data to the document with every modification, but never deletes anything to keep the history. Old data is moved when there are 1000 commits to be moved or the document is bigger than 1 MB. A document with a reference to old data looks like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_deleted&quot; : {
         &quot;r13fcda88ac0-0-1&quot; : &quot;false&quot;,
     },
@@ -538,7 +540,7 @@ nodes
 <p>The optional sub-document <tt>_prev</tt> contains a list of revision pairs, each indicating the range of commit revisions a previous document contains. In the above example there is one document with previous commits from <tt>r13fcda88ae0-0-1</tt> to <tt>r13fcda91710-0-1</tt>. The id of the previous document is derived from the upper bound of the range and the id/path of the current document. The id of the previous document for <tt>r13fcda88ae0-0-1</tt> and <tt>0:/</tt> is <tt>1:p/r13fcda88ae0-0-1</tt> and may looks like this:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">{
+<div class="source"><pre class="prettyprint">{
     &quot;_id&quot; : &quot;1:p/r13fcda88ae0-0-1&quot;,
     &quot;_modCount&quot; : NumberLong(1),
     &quot;_revisions&quot; : {
@@ -585,7 +587,7 @@ nodes
 <p>Each running cluster node updates the lease time of the cluster node id once every minute, to ensure each cluster node uses a different cluster node id.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&gt; db.clusterNodes.find().pretty()
+<div class="source"><pre class="prettyprint">&gt; db.clusterNodes.find().pretty()
 
 {
     &quot;_id&quot; : &quot;1&quot;,
@@ -614,7 +616,7 @@ nodes
 <p>In this mode the config is specified as part of the Mongo URI (See <a href="../osgi_config.html#document-node-store">configuration</a>). So if a user wants that reads from secondaries should prefer secondary with tag <i>dc:ny,rack:1</i> otherwise they go to other secondary then he can specify that via following mongouri</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">mongodb://example1.com,example2.com,example3.com/?readPreference=secondary&amp;readPreferenceTags=dc:ny,rack:1&amp;readPreferenceTags=dc:ny&amp;readPreferenceTags= 
+<div class="source"><pre class="prettyprint">mongodb://example1.com,example2.com,example3.com/?readPreference=secondary&amp;readPreferenceTags=dc:ny,rack:1&amp;readPreferenceTags=dc:ny&amp;readPreferenceTags= 
 </pre></div></div>
 <p>Refer to <a class="externalLink" href="http://docs.mongodb.org/manual/reference/connection-string/#read-preference-options">Read Preference Options</a> and <a class="externalLink" href="http://docs.mongodb.org/manual/reference/connection-string/#write-concern-options">Write Concern Options</a> for more details. </p></div>
 <div class="section">
@@ -622,7 +624,7 @@ nodes
 <p>The read preference and write concern of all cluster nodes can be changed at runtime without having to restart the instances, by setting the property <tt>readWriteMode</tt> of this collection. All cluster nodes will pick up the change within one minute (when they renew the lease of the cluster node id). This is a string property with the format <tt>'readPreference=&lt;preference&gt;&amp;w=&lt;writeConcern&gt;'</tt> similar to the way it is used in mongouri. Just that it does not include other option details. The following shell command will set the read preference to <tt>primary</tt> and the write concern to <tt>majority</tt> for all cluster nodes:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&gt; db.clusterNodes.update({}, 
+<div class="source"><pre class="prettyprint">&gt; db.clusterNodes.update({}, 
   {$set: {readWriteMode:'readPreference=primary&amp;w=majority'}}, 
   {multi: true})    
 </pre></div></div></div></div></div>
@@ -686,7 +688,7 @@ nodes
 <p>Upgrading to a newer Oak version may therefore first require an update of the format version before a newer version of a DocumentNodeStore can be started on existing data. The oak-run tools contains an <tt>unlockUpgrade</tt> mode to perform this operation. Use the oak-run tool with the version matching the target upgrade version to unlock an upgrade with the following command. The below example unlocks an upgrade to 1.8 with a DocumentNodeStore on MongoDB:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&gt; java -jar oak-run-1.8.0.jar unlockUpgrade mongodb://example.com:27017/oak
+<div class="source"><pre class="prettyprint">&gt; java -jar oak-run-1.8.0.jar unlockUpgrade mongodb://example.com:27017/oak
 </pre></div></div>
 <p>Please note that unlocking an upgrade is only possible when all cluster nodes are inactive, otherwise the command will refuse to change the format version.</p></div>
 <div class="section">
@@ -708,7 +710,7 @@ nodes
 <p>The first two options are not described in more detail, because both of them are simple method calls. The third option comes with some sub commands as described below when oak-run with the <tt>revisions</tt> run mode is invoked without parameters or options:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">revisions mongodb://host:port/database &lt;sub-command&gt; [options]
+<div class="source"><pre class="prettyprint">revisions mongodb://host:port/database &lt;sub-command&gt; [options]
 where sub-command is one of
   info     give information about the revisions state without performing
            any modifications
@@ -737,7 +739,7 @@ Option                 Description
 <p>A revision garbage collection can be invoked while the system is online and running. Using the oak-run runnable jar, a revision GC on a system using the MongoDB backend can be initiated with:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run-1.8.0.jar revisions mongodb://localhost:27017/oak collect
+<div class="source"><pre class="prettyprint">java -jar oak-run-1.8.0.jar revisions mongodb://localhost:27017/oak collect
 </pre></div></div>
 <p>This will collect changes identified as garbage, which is older than 24 hours.</p></div>
         </div>

Modified: jackrabbit/site/live/oak/docs/nodestore/overview.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/overview.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/overview.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/overview.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>

Modified: jackrabbit/site/live/oak/docs/nodestore/persistent-cache.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/persistent-cache.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/persistent-cache.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/persistent-cache.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -236,7 +238,7 @@
 <p>The default OSGi configuration of the persistent cache is:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
+<div class="source"><pre class="prettyprint">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
     persistentCache=&quot;cache,binary\=0&quot;
 </pre></div></div>
 <p>Oak version up to 1.4 have the persistent cache disabled by default, which is equivalent with a configuration entry set to an empty String. Starting with Oak 1.6, the persistent cache is enabled by default and can be disabled by setting the configuration entry to <tt>&quot;-&quot;</tt>.</p></div>
@@ -245,7 +247,7 @@
 <p>The persistent cache configuration setting is string with a number of comma separated elements. The first element is the directory where the cache is stored. Example:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&quot;cache&quot;
+<div class="source"><pre class="prettyprint">&quot;cache&quot;
 </pre></div></div>
 <p>In this case, the data is stored in the directory &#x201c;cache&#x201d;, relative to the <tt>repository.home</tt> directory. If no repository home directory is configured, the directory is relative to the current working directory. Oak versions prior to 1.6 always resolve to the current working directory and ignore the <tt>repository.home</tt> configuration. By default, there are at most two files (two generations) with the name &#x201c;cache-x.data&#x201d;, where x is an incrementing number (0, 1,&#x2026;). A file is at most 1 GB by default. If the file is larger, the next file is created, and if there are more than two files, the oldest one is removed. If data from the older file is accessed, it is copied to the latest file. That way, data that is not recently read will eventually be removed.</p>
 <p>The following other configuration options are available:</p>
@@ -276,12 +278,12 @@
 <p>Those setting can be appended to the persistent cache configuration string. An example configuration is:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&quot;cache,size\=2048,binary\=0,-compact,-compress&quot;
+<div class="source"><pre class="prettyprint">&quot;cache,size\=2048,binary\=0,-compact,-compress&quot;
 </pre></div></div>
 <p>To disable the persistent cache entirely in Oak 1.6 and newer, use the following configuration:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
+<div class="source"><pre class="prettyprint">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
     persistentCache=&quot;-&quot;
 </pre></div></div>
 <p>Up to Oak version 1.4, either omit the persistentCache entry or set it to an empty String to disable the persistent cache.</p></div>
@@ -291,7 +293,7 @@
 <p>Diff cache entries can also are stored in a separate persistent cache and configured independently if needed. This can be done in the OSGi configuration like in the following example:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
+<div class="source"><pre class="prettyprint">org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService
     persistentCache=&quot;cache,size\=2048&quot;
     journalCache=&quot;diff-cache,size\=1024&quot;
 </pre></div></div>
@@ -301,7 +303,7 @@
 <p>Internally, the persistent cache uses a key-value store (basically a java.util.Map), which is persisted to disk. The current key-value store backend is the <a class="externalLink" href="http://www.h2database.com/html/mvstore.html">H2 MVStore</a>. This library is only needed if the persistent cache is configured. Version 1.4.185 or newer is needed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">&lt;dependency&gt;
+<div class="source"><pre class="prettyprint">&lt;dependency&gt;
     &lt;groupId&gt;com.h2database&lt;/groupId&gt;
     &lt;artifactId&gt;h2-mvstore&lt;/artifactId&gt;
     &lt;version&gt;1.4.185&lt;/version&gt;

Modified: jackrabbit/site/live/oak/docs/nodestore/segment/changes.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segment/changes.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segment/changes.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segment/changes.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>

Modified: jackrabbit/site/live/oak/docs/nodestore/segment/classes.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segment/classes.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segment/classes.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segment/classes.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>

Modified: jackrabbit/site/live/oak/docs/nodestore/segment/overview.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segment/overview.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segment/overview.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segment/overview.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -359,40 +361,40 @@
 <p>Every log message generated during the garbage collection process includes a sequence number indicating how many times garbage collection ran since the system started. The sequence number is always printed at the beginning of the message like in the following example.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: ...
+<div class="source"><pre class="prettyprint">TarMK GC #2: ...
 </pre></div></div>
 <div class="section">
 <h5><a name="When_did_garbage_collection_start"></a><a name="when-did-garbage-collection-start"></a> When did garbage collection start?</h5>
 <p>As soon as garbage collection is triggered, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: started
+<div class="source"><pre class="prettyprint">TarMK GC #2: started
 </pre></div></div></div>
 <div class="section">
 <h5><a name="When_did_estimation_start"></a><a name="when-did-estimation-start"></a> When did estimation start?</h5>
 <p>As soon as the estimation phase of garbage collection starts, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: estimation started
+<div class="source"><pre class="prettyprint">TarMK GC #2: estimation started
 </pre></div></div></div>
 <div class="section">
 <h5><a name="Is_estimation_disabled"></a><a name="is-estimation-disabled"></a> Is estimation disabled?</h5>
 <p>The estimation phase can be disabled by configuration. If this is the case, the system prints the following message.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: estimation skipped because it was explicitly disabled
+<div class="source"><pre class="prettyprint">TarMK GC #2: estimation skipped because it was explicitly disabled
 </pre></div></div>
 <p>Estimation is also skipped when compaction is disabled on the system. In this case, the following message is printed instead.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: estimation skipped because compaction is paused
+<div class="source"><pre class="prettyprint">TarMK GC #2: estimation skipped because compaction is paused
 </pre></div></div></div>
 <div class="section">
 <h5><a name="Was_estimation_cancelled"></a><a name="was-estimation-cancelled"></a> Was estimation cancelled?</h5>
 <p>The execution of the estimation phase can be cancelled manually by the user or automatically if certain events occur. If estimation is cancelled, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: estimation interrupted: ${REASON}. Skipping compaction.
+<div class="source"><pre class="prettyprint">TarMK GC #2: estimation interrupted: ${REASON}. Skipping compaction.
 </pre></div></div>
 <p>The placeholder <tt>${REASON}</tt> is not actually printed in the message, but will be substituted by a more specific description of the reason that brought estimation to a premature halt. As stated before, some external events can terminate estimation, e.g. not enough memory or disk space on the host system. Moreover, estimation can also be cancelled by shutting down the system or by explicitly cancelling it via administrative interfaces. In each of these cases, the reason why estimation is cancelled will be printed in the log.</p></div>
 <div class="section">
@@ -400,7 +402,7 @@
 <p>When estimation terminates, either because of external cancellation or after a successful execution, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: estimation completed in 961.8 &#x3bc;s (0 ms). ${RESULT}
+<div class="source"><pre class="prettyprint">TarMK GC #2: estimation completed in 961.8 &#x3bc;s (0 ms). ${RESULT}
 </pre></div></div>
 <p>Moreover, the duration of the estimation phase is printed both in a readable format and in milliseconds. The placeholder <tt>${RESULT}</tt> stands for a message that depends on the estimation strategy.</p></div>
 <div class="section">
@@ -408,7 +410,7 @@
 <p>When the compaction phase of the garbage collection process starts, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction started, gc options=SegmentGCOptions{paused=false, estimationDisabled=false, gcSizeDeltaEstimation=1, retryCount=5, forceTimeout=3600, retainedGenerations=2, gcSizeDeltaEstimation=1}
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction started, gc options=SegmentGCOptions{paused=false, estimationDisabled=false, gcSizeDeltaEstimation=1, retryCount=5, forceTimeout=3600, retainedGenerations=2, gcSizeDeltaEstimation=1}
 </pre></div></div>
 <p>The message includes a dump of the garbage collection options that are used during the compaction phase.</p></div>
 <div class="section">
@@ -416,7 +418,7 @@
 <p>The compaction phase can be skipped by pausing the garbage collection process. If compaction is paused, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction paused
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction paused
 </pre></div></div>
 <p>As long as compaction is paused, neither the estimation phase nor the compaction phase will be executed.</p></div>
 <div class="section">
@@ -424,7 +426,7 @@
 <p>The compaction phase can be cancelled manually by the user or automatically because of external events. If compaction is cancelled, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction cancelled: ${REASON}.
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction cancelled: ${REASON}.
 </pre></div></div>
 <p>The placeholder <tt>${REASON}</tt> is not actually printed in the message, but will be substituted by a more specific description of the reason that brought compaction to a premature halt. As stated before, some external events can terminate compaction, e.g. not enough memory or disk space on the host system. Moreover, compaction can also be cancelled by shutting down the system or by explicitly cancelling it via administrative interfaces. In each of these cases, the reason why compaction is cancelled will be printed in the log.</p></div>
 <div class="section">
@@ -432,22 +434,22 @@
 <p>When compaction complete successfully, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction succeeded in 6.580 min (394828 ms), after 2 cycles
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction succeeded in 6.580 min (394828 ms), after 2 cycles
 </pre></div></div>
 <p>The time shown in the log message is relative to the compaction phase only. The reference to the amount of cycles spent for the compaction phase is explained in more detail below. If compaction did not complete successfully, the following message is printed instead.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction failed in 32.902 min (1974140 ms), after 5 cycles
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction failed in 32.902 min (1974140 ms), after 5 cycles
 </pre></div></div>
 <p>This message doesn&#x2019;t mean that there was an unrecoverable error, but only that compaction gave up after a certain amount of attempts. In case an error occurs, the following message is printed instead.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction encountered an error
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction encountered an error
 </pre></div></div>
 <p>This message is followed by the stack trace of the exception that was caught during the compaction phase. There is also a special message that is printed if the thread running the compaction phase is interrupted.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction interrupted
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction interrupted
 </pre></div></div></div>
 <div class="section">
 <h5><a name="How_does_compaction_work_with_concurrent_writes"></a><a name="how-does-compaction-works-with-concurrent-writes"></a> How does compaction work with concurrent writes?</h5>
@@ -455,45 +457,45 @@
 <p>When compaction first tries to setup the new generation, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction cycle 0 completed in 6.580 min (394828 ms). Compacted 3e3b35d3-2a15-43bc-a422-7bd4741d97a5.0000002a to 348b9500-0d67-46c5-a683-3ea8b0e6c21c.000012c0
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction cycle 0 completed in 6.580 min (394828 ms). Compacted 3e3b35d3-2a15-43bc-a422-7bd4741d97a5.0000002a to 348b9500-0d67-46c5-a683-3ea8b0e6c21c.000012c0
 </pre></div></div>
 <p>The message shows how long it took to compact the data to the new generation. It also prints the record identifiers of the two head states. The head state on the left belongs to the previous generation, the one on the right to the new.</p>
 <p>If concurrent commits are detected, compaction tries to incorporate those changes in the new generation. In this case, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction detected concurrent commits while compacting. Compacting these commits. Cycle 1 of 5
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction detected concurrent commits while compacting. Compacting these commits. Cycle 1 of 5
 </pre></div></div>
 <p>This message means that a new compaction cycle is automatically started. Compaction will try to incorporate new changes for a certain amount of cycles, where the exact amount of cycles is a configuration option. After every compaction cycle, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction cycle 1 completed in 6.580 min (394828 ms). Compacted 4d22b170-f8b7-406b-a2fc-45bf782440ac.00000065 against 3e3b35d3-2a15-43bc-a422-7bd4741d97a5.0000002a to 72e60037-f917-499b-a476-607ea6f2735c.00000d0d
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction cycle 1 completed in 6.580 min (394828 ms). Compacted 4d22b170-f8b7-406b-a2fc-45bf782440ac.00000065 against 3e3b35d3-2a15-43bc-a422-7bd4741d97a5.0000002a to 72e60037-f917-499b-a476-607ea6f2735c.00000d0d
 </pre></div></div>
 <p>This message contains three record identifiers instead of two. This is because the initial state that was being compacted evolved into a different one due to the concurrent commits. The message makes clear that the concurrent changes referenced from the first record identifier, up to the changes referenced from the second identifier, where moved to the new generation and are now referenced from third identifier.</p>
 <p>If the system is under heavy load and too many concurrent commits are generated, compaction might fail to catch up. In this case, a message like the following is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction gave up compacting concurrent commits after 5 cycles.
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction gave up compacting concurrent commits after 5 cycles.
 </pre></div></div>
 <p>The message means that compaction tried to compact the repository data to the new generation for five times, but every time there were concurrent changes that prevented compaction from completion. To prevent the system from being too overloaded with background activity, compaction stopped itself after the configured amount of cycles.</p>
 <p>At this point the system can be configured to obtain exclusive access of the system and force compaction to complete. This means that if compaction gave up after the configured number of cycles, it would take full control over the repository and block concurrent writes. If the system is configured to behave this way, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: trying to force compact remaining commits for 60 seconds. Concurrent commits to the store will be blocked.
+<div class="source"><pre class="prettyprint">TarMK GC #2: trying to force compact remaining commits for 60 seconds. Concurrent commits to the store will be blocked.
 </pre></div></div>
 <p>If, after taking exclusive control of the repository for the specified amount of time, compaction completes successfully, the following message will be printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction succeeded to force compact remaining commits after 56.7 s (56722 ms).
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction succeeded to force compact remaining commits after 56.7 s (56722 ms).
 </pre></div></div>
 <p>Sometimes the amount of time allocated to the compaction phase in exclusive mode is not enough. It might happen that compaction is not able to complete its work in the allocated time. If this happens, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction failed to force compact remaining commits after 6.580 min (394828 ms). Most likely compaction didn't get exclusive access to the store.
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction failed to force compact remaining commits after 6.580 min (394828 ms). Most likely compaction didn't get exclusive access to the store.
 </pre></div></div>
 <p>Even if compaction takes exclusive access to the repository, it can still be interrupted. In this case, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: compaction failed to force compact remaining commits after 6.580 min (394828 ms). Compaction was cancelled: ${REASON}.
+<div class="source"><pre class="prettyprint">TarMK GC #2: compaction failed to force compact remaining commits after 6.580 min (394828 ms). Compaction was cancelled: ${REASON}.
 </pre></div></div>
 <p>The placeholder <tt>${REASON}</tt> will be substituted with a more detailed description of the reason why compaction was stopped.</p></div>
 <div class="section">
@@ -501,14 +503,14 @@
 <p>When the cleanup phase of the garbage collection process starts, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: cleanup started.
+<div class="source"><pre class="prettyprint">TarMK GC #2: cleanup started.
 </pre></div></div></div>
 <div class="section">
 <h5><a name="Was_cleanup_cancelled"></a><a name="was-cleanup-cancelled"></a> Was cleanup cancelled?</h5>
 <p>If cleanup is cancelled, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: cleanup interrupted
+<div class="source"><pre class="prettyprint">TarMK GC #2: cleanup interrupted
 </pre></div></div>
 <p>There is no way to cancel cleanup manually. The only time cleanup can be cancel is when shutting down the repository.</p></div>
 <div class="section">
@@ -516,7 +518,7 @@
 <p>When cleanup completes, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: cleanup completed in 16.23 min (974079 ms). Post cleanup size is 10.4 GB (10392082944 bytes) and space reclaimed 84.5 GB (84457663488 bytes).
+<div class="source"><pre class="prettyprint">TarMK GC #2: cleanup completed in 16.23 min (974079 ms). Post cleanup size is 10.4 GB (10392082944 bytes) and space reclaimed 84.5 GB (84457663488 bytes).
 </pre></div></div>
 <p>The message includes the time the cleanup phase took to complete, both in a human readable format and in milliseconds. Next the final size of the repository is shown, followed by the amount of space that was reclaimed during the cleanup phase. Both the final size and the reclaimed space are shown in human readable form and in bytes.</p></div>
 <div class="section">
@@ -524,23 +526,23 @@
 <p>The first thing cleanup does is printing out the current size of the repository with a message similar to the following.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #1: current repository size is 89.3 GB (89260786688 bytes)
+<div class="source"><pre class="prettyprint">TarMK GC #1: current repository size is 89.3 GB (89260786688 bytes)
 </pre></div></div>
 <p>After that, the cleanup phase will iterate through every TAR file and figure out which segments are still in use and which ones can be reclaimed. Cleanup will print a sequence of messages like the following.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">data00000a.tar: size of bulk references/reclaim set 0/6
+<div class="source"><pre class="prettyprint">data00000a.tar: size of bulk references/reclaim set 0/6
 </pre></div></div>
 <p>The first part of the message is the TAR file analyzed last. The two numbers at the end give an idea of how many references to segments are being (transitively) followed and how many of them point to bulk segments that can be removed.</p>
 <p>After the cleanup phase scanned the repository, TAR files are purged of unused segments. In some cases, a TAR file would end up containing no segments at all. In this case, the TAR file is marked for deletion and the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">TarMK GC #2: cleanup marking files for deletion: data00000a.tar
+<div class="source"><pre class="prettyprint">TarMK GC #2: cleanup marking files for deletion: data00000a.tar
 </pre></div></div>
 <p>Please note that this message doesn&#x2019;t mean that cleanup will physically remove the file right now. The file is only being marked as deletable. Another background task will periodically kick in and remove unused files from disk. When this happens, the following message is printed.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">Removed files data00000a.tar,data00001a.tar,data00002a.tar
+<div class="source"><pre class="prettyprint">Removed files data00000a.tar,data00001a.tar,data00002a.tar
 </pre></div></div>
 <p>The output of this message can vary. It depends on the amount of segments that were cleaned up, on how many TAR files were emptied and on how often the background activity removes unused files.</p></div></div>
 <div class="section">
@@ -601,27 +603,27 @@
 <h3><a name="Backup"></a><a name="backup"></a> Backup</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar backup ORIGINAL BACKUP 
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar backup ORIGINAL BACKUP 
 </pre></div></div>
 <p>The <tt>backup</tt> tool performs a backup of a Segment Store <tt>ORIGINAL</tt> and saves it to the folder <tt>BACKUP</tt>. <tt>ORIGINAL</tt> must be the path to an existing, valid Segment Store. <tt>BACKUP</tt> must be a valid path to a folder on the file system. If <tt>BACKUP</tt> doesn&#x2019;t exist, it will be created. If <tt>BACKUP</tt> exists, it must be a path to an existing, valid Segment Store.</p>
 <p>The tool assumes that the <tt>ORIGINAL</tt> Segment Store doesn&#x2019;t use an external Blob Store. If this is the case, it&#x2019;s necessary to set the <tt>oak.backup.UseFakeBlobStore</tt> system property to <tt>true</tt> on the command line as shown below.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -Doak.backup.UseFakeBlobStore=true -jar oak-run.jar backup ...
+<div class="source"><pre class="prettyprint">java -Doak.backup.UseFakeBlobStore=true -jar oak-run.jar backup ...
 </pre></div></div>
 <p>When a backup is performed, if <tt>BACKUP</tt> points to an existing Segment Store, only the content that is different from <tt>ORIGINAL</tt> is copied. This is similar to an incremental backup performed at the level of the content. When an incremental backup is performed, the tool will automatically try to cleanup eventual garbage from the <tt>BACKUP</tt> Segment Store.</p></div>
 <div class="section">
 <h3><a name="Restore"></a><a name="restore"></a> Restore</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar restore ORIGINAL BACKUP
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar restore ORIGINAL BACKUP
 </pre></div></div>
 <p>The <tt>restore</tt> tool restores the state of the <tt>ORIGINAL</tt> Node Store from a previous backup <tt>BACKUP</tt>. This tool is the counterpart of <tt>backup</tt>.</p></div>
 <div class="section">
 <h3><a name="Check"></a><a name="check"></a> Check</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar check PATH [--journal JOURNAL] [--notify SECS] [--bin] [--filter PATH1[,PATH2,..,PATHn]] [--io-stats]
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar check PATH [--journal JOURNAL] [--notify SECS] [--bin] [--filter PATH1[,PATH2,..,PATHn]] [--io-stats]
 </pre></div></div>
 <p>The <tt>check</tt> tool inspects an existing Segment Store at <tt>PATH</tt> for eventual inconsistencies. The algorithm implemented by this tool traverses every revision in the journal, from the most recent to the oldest. For every revision, the actual nodes and properties are traversed, verifying that every piece of data is reachable and undamaged. A deep scan of the content tree, traversing every node, will be performed by default.</p>
 <p>If the <tt>--journal</tt> option is specified, the tool will use the journal file at <tt>JOURNAL</tt> instead of picking up the one contained in <tt>PATH</tt>. <tt>JOURNAL</tt> must be a path to a valid journal file for the Segment Store. </p>
@@ -633,14 +635,14 @@
 <h3><a name="Compact"></a><a name="compact"></a> Compact</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar compact PATH
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar compact PATH
 </pre></div></div>
 <p>The <tt>compact</tt> command performs offline compaction on the Segment Store at <tt>PATH</tt>. <tt>PATH</tt> must be a valid path to an existing Segment Store. </p></div>
 <div class="section">
 <h3><a name="Debug"></a><a name="debug"></a> Debug</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar debug PATH
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar debug PATH
 java -jar oak-run.jar debug PATH ITEMS...
 </pre></div></div>
 <p>The <tt>debug</tt> command prints diagnostic information about a Segment Store or individual Segment Store items.</p>
@@ -654,7 +656,7 @@ java -jar oak-run.jar debug PATH ITEMS..
 <h3><a name="Diff"></a><a name="diff"></a> Diff</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar tarmkdiff [--output OUTPUT] --list PATH
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar tarmkdiff [--output OUTPUT] --list PATH
 java -jar oak-run.jar tarmkdiff [--output OUTPUT] [--incremental] [--path NODE] [--ignore-snfes] --diff REVS PATH
 </pre></div></div>
 <p>The <tt>diff</tt> command prints content diffs between revisions in the Segment Store at <tt>PATH</tt>.</p>
@@ -669,7 +671,7 @@ java -jar oak-run.jar tarmkdiff [--outpu
 <h3><a name="History"></a><a name="history"></a> History</h3>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">java -jar oak-run.jar history [--journal JOURNAL] [--path NODE] [--depth DEPTH] PATH
+<div class="source"><pre class="prettyprint">java -jar oak-run.jar history [--journal JOURNAL] [--path NODE] [--depth DEPTH] PATH
 </pre></div></div>
 <p>The <tt>history</tt> command shows how the content of a node or of a sub-tree changed over time in the Segment Store at <tt>PATH</tt>.</p>
 <p>The history of the node is computed based on the revisions reported by the journal in the Segment Store. If a different set of revisions needs to be used, it is possible to specify a custom journal file by using the <tt>--journal</tt> option. If this option is used, <tt>JOURNAL</tt> must be a path to a valid journal file.</p>

Modified: jackrabbit/site/live/oak/docs/nodestore/segment/records.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segment/records.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segment/records.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segment/records.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -246,7 +248,7 @@
 <p>Bulk segments contain raw binary data, interpreted simply as a sequence of block records with no headers or other extra metadata:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">[block 1] [block 2] ... [block N]
+<div class="source"><pre class="prettyprint">[block 1] [block 2] ... [block N]
 </pre></div></div>
 <p>A bulk segment whose length is <tt>n</tt> bytes consists of <tt>n div 4096</tt> block records of 4KiB each followed possibly a block record of <tt>n mod 4096</tt> bytes, if there still are remaining bytes in the segment. The structure of a bulk segment can thus be determined based only on the segment length.</p></div>
 <div class="section">
@@ -258,13 +260,13 @@
 <p>The overall structure of a data segment is:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">[segment header] [record 1] [record 2] ... [record N]
+<div class="source"><pre class="prettyprint">[segment header] [record 1] [record 2] ... [record N]
 </pre></div></div>
 <p>The segment header and each record is zero-padded to make their size a multiple of four bytes and to align the next record at a four-byte boundary.</p>
 <p>The segment header consists of the following fields. All integers are stored in big endian format.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+---------+---------+---------+---------+---------+---------+---------+---------+
+<div class="source"><pre class="prettyprint">+---------+---------+---------+---------+---------+---------+---------+---------+
 | magic bytes: &quot;0aK&quot;          | version | reserved                               
 +---------+---------+---------+---------+---------+---------+---------+---------+
   reserved          | generation                            | segrefcount            
@@ -298,7 +300,7 @@
 <p>The offset is relative to the beginning of a theoretical segment which is defined to be 256 KiB. Since records are added from the bottom of a segment to the top (i.e. from higher to lower offsets), and since segments could be shrunk down to be smaller than 256 KiB, the offset has to be normalized with to the following formula.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">SIZE - 256 KiB + OFFSET
+<div class="source"><pre class="prettyprint">SIZE - 256 KiB + OFFSET
 </pre></div></div>
 <p><tt>SIZE</tt> is the actual size of the segment under inspection, and <tt>OFFSET</tt> is the offset looked up from the record references table. The normalized offset can be used to locate the position of the record in the current segment.</p></div>
 <div class="section">
@@ -343,7 +345,7 @@
 </ul>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+--------+--------+--------+-----+
+<div class="source"><pre class="prettyprint">+--------+--------+--------+-----+
 | sub-list ID 1            | ... |
 +--------+--------+--------+-----+
   |
@@ -378,7 +380,7 @@
 <p>A template record consists of a set of up to N (exact size TBD, N ~ 256) property name and type pairs. Additionally, since nodes that are empty or contain just a single child node are most common, a template record also contains information whether the node has zero, one or many child nodes. In case of a single child node, the template also contains the name of that node. For example, the template for typical mix:versionable nt:file nodes would be (using CND-like notation):</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">- jcr:primaryType (NAME)
+<div class="source"><pre class="prettyprint">- jcr:primaryType (NAME)
 - jcr:mixinTypes (NAME) multiple
 - jcr:created (DATE)
 - jcr:uuid (STRING)

Modified: jackrabbit/site/live/oak/docs/nodestore/segment/tar.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segment/tar.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segment/tar.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segment/tar.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>

Modified: jackrabbit/site/live/oak/docs/nodestore/segmentmk.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/segmentmk.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/nodestore/segmentmk.html (original)
+++ jackrabbit/site/live/oak/docs/nodestore/segmentmk.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>
@@ -260,7 +262,7 @@
 <p>Bulk segments contain raw binary data, interpreted simply as a sequence of block records with no headers or other extra metadata:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">[block 1] [block 2] ... [block N]
+<div class="source"><pre class="prettyprint">[block 1] [block 2] ... [block N]
 </pre></div></div>
 <p>A bulk segment whose length is <tt>n</tt> bytes consists of <tt>n div 4096</tt> block records of 4KiB each followed possibly a block record of <tt>n mod 4096</tt> bytes, if there still are remaining bytes in the segment. The structure of a bulk segment can thus be determined based only on the segment length.</p></div>
 <div class="section">
@@ -268,13 +270,13 @@
 <p>A data segment can contain any types of records, may refer to content in other segments, and comes with a segment header that guides the parsing of the segment. The overall structure of a data segment is:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">[segment header] [record 1] [record 2] ... [record N]
+<div class="source"><pre class="prettyprint">[segment header] [record 1] [record 2] ... [record N]
 </pre></div></div>
 <p>The header and each record is zero-padded to make their size a multiple of four bytes and to align the next record at a four-byte boundary.</p>
 <p>The segment header consists of the following fields:</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+--------+--------+--------+--------+--------+--------+--------+--------+
+<div class="source"><pre class="prettyprint">+--------+--------+--------+--------+--------+--------+--------+--------+
 | magic bytes: &quot;0aK&quot; ASCII |version |reserved|idcount |rootcount        |
 +--------+--------+--------+--------+--------+--------+--------+--------+
 | blobrefcount    | reserved (set to 0)                                 |
@@ -312,7 +314,7 @@
 <p>Each record is uniquely addressable by its location within the segment and the UUID of that segment. A single segment can contain up to 256KiB of data and and references to up to 256 segments (including itself). Since all records are aligned at four-byte boundaries, 16 bits are needed to address all possible record locations within a segment. Thus only three bytes are needed to store a reference to any record in any segment (1 byte to identify the segment, 2 bytes for the record offset):</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+--------+--------+--------+
+<div class="source"><pre class="prettyprint">+--------+--------+--------+
 | refid  | offset          |
 +--------+--------+--------+
 </pre></div></div>
@@ -326,7 +328,7 @@
 <p>The list of references is split into pieces of up to 255 references each and those pieces are stored as records. If there are more than 255 pieces like that, then a higher-level list is created of references to those pieces. This process is continued until the resulting list has less than 255 entries.</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">+--------+--------+--------+-----+
+<div class="source"><pre class="prettyprint">+--------+--------+--------+-----+
 | sub-list ID 1            | ... |
 +--------+--------+--------+-----+
   |
@@ -364,7 +366,7 @@
 <p>A template record consists of a set of up to N (exact size TBD, N ~ 256) property name and type pairs. Additionally, since nodes that are empty or contain just a single child node are most common, a template record also contains information whether the node has zero, one or many child nodes. In case of a single child node, the template also contains the name of that node. For example, the template for typical mix:versionable nt:file nodes would be (using CND-like notation):</p>
 
 <div class="source">
-<div class="source"><pre class="prettyprint linenums">- jcr:primaryType (NAME)
+<div class="source"><pre class="prettyprint">- jcr:primaryType (NAME)
 - jcr:mixinTypes (NAME) multiple
 - jcr:created (DATE)
 - jcr:uuid (STRING)

Modified: jackrabbit/site/live/oak/docs/oak-mongo-js/index.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/oak-mongo-js/index.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/oak-mongo-js/index.html (original)
+++ jackrabbit/site/live/oak/docs/oak-mongo-js/index.html Tue May  2 13:04:22 2017
@@ -56,7 +56,7 @@
 <br class="clear">
 
 <footer>
-    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 11:58:13 GMT+0200 (CEST)
+    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 15:01:28 GMT+0200 (CEST)
 </footer>
 
 <script> prettyPrint(); </script>

Modified: jackrabbit/site/live/oak/docs/oak-mongo-js/oak-mongo.js.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/oak-mongo-js/oak-mongo.js.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/oak-mongo-js/oak-mongo.js.html (original)
+++ jackrabbit/site/live/oak/docs/oak-mongo-js/oak-mongo.js.html Tue May  2 13:04:22 2017
@@ -1066,7 +1066,7 @@ var oak = (function(global){
 <br class="clear">
 
 <footer>
-    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 11:58:13 GMT+0200 (CEST)
+    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 15:01:28 GMT+0200 (CEST)
 </footer>
 
 <script> prettyPrint(); </script>

Modified: jackrabbit/site/live/oak/docs/oak-mongo-js/oak.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/oak-mongo-js/oak.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/oak-mongo-js/oak.html (original)
+++ jackrabbit/site/live/oak/docs/oak-mongo-js/oak.html Tue May  2 13:04:22 2017
@@ -4114,7 +4114,7 @@ is inactive.
 <br class="clear">
 
 <footer>
-    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 11:58:13 GMT+0200 (CEST)
+    Documentation generated by <a href="https://github.com/jsdoc3/jsdoc">JSDoc 3.3.2</a> on Tue May 02 2017 15:01:28 GMT+0200 (CEST)
 </footer>
 
 <script> prettyPrint(); </script>

Modified: jackrabbit/site/live/oak/docs/oak_api/error_codes.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/oak_api/error_codes.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/oak_api/error_codes.html (original)
+++ jackrabbit/site/live/oak/docs/oak_api/error_codes.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -168,6 +169,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>

Modified: jackrabbit/site/live/oak/docs/oak_api/overview.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/oak_api/overview.html?rev=1793486&r1=1793485&r2=1793486&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/oak_api/overview.html (original)
+++ jackrabbit/site/live/oak/docs/oak_api/overview.html Tue May  2 13:04:22 2017
@@ -70,6 +70,7 @@
 <a href="../query/query.html" title="Query">Query</a>
               <ul class="dropdown-menu">
                   <li><a href="../query/query-engine.html" title="Query Engine">Query Engine</a></li>
+                  <li><a href="../query/query-troubleshooting.html" title="Troubleshooting">Troubleshooting</a></li>
                   <li><a href="../query/indexing.html" title="Indexing">Indexing</a></li>
                   <li><a href="../query/lucene.html" title="Lucene Index">Lucene Index</a></li>
                   <li><a href="../query/property-index.html" title="Property Index">Property Index</a></li>
@@ -169,6 +170,7 @@
     <li><a href="../query/query.html" title="Query"><span class="icon-chevron-down"></span>Query</a>
       <ul class="nav nav-list">
     <li><a href="../query/query-engine.html" title="Query Engine"><span class="none"></span>Query Engine</a>  </li>
+    <li><a href="../query/query-troubleshooting.html" title="Troubleshooting"><span class="none"></span>Troubleshooting</a>  </li>
     <li><a href="../query/indexing.html" title="Indexing"><span class="none"></span>Indexing</a>  </li>
     <li><a href="../query/lucene.html" title="Lucene Index"><span class="none"></span>Lucene Index</a>  </li>
     <li><a href="../query/property-index.html" title="Property Index"><span class="none"></span>Property Index</a>  </li>



Mime
View raw message