jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thom...@apache.org
Subject svn commit: r1851606 - in /jackrabbit/site/live/oak/docs: query/query-engine.html release-schedule.html
Date Fri, 18 Jan 2019 08:02:41 GMT
Author: thomasm
Date: Fri Jan 18 08:02:41 2019
New Revision: 1851606

URL: http://svn.apache.org/viewvc?rev=1851606&view=rev
Log:
OAK-936: Site checkin for project Oak Documentation-1.10-SNAPSHOT

Modified:
    jackrabbit/site/live/oak/docs/query/query-engine.html
    jackrabbit/site/live/oak/docs/release-schedule.html

Modified: jackrabbit/site/live/oak/docs/query/query-engine.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/query/query-engine.html?rev=1851606&r1=1851605&r2=1851606&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/query/query-engine.html (original)
+++ jackrabbit/site/live/oak/docs/query/query-engine.html Fri Jan 18 08:02:41 2019
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 at 2019-01-08 
+ | Generated by Apache Maven Doxia Site Renderer 1.8.1 at 2019-01-18 
  | Rendered using Apache Maven Fluido Skin 1.6
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20190108" />
+    <meta name="Date-Revision-yyyymmdd" content="20190118" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Jackrabbit Oak &#x2013; The Query Engine</title>
     <link rel="stylesheet" href="../css/apache-maven-fluido-1.6.min.css" />
@@ -142,7 +142,7 @@
 
       <div id="breadcrumbs">
         <ul class="breadcrumb">
-        <li id="publishDate">Last Published: 2019-01-08<span class="divider">|</span>
+        <li id="publishDate">Last Published: 2019-01-18<span class="divider">|</span>
 </li>
           <li id="projectVersion">Version: 1.10-SNAPSHOT</li>
         </ul>
@@ -465,7 +465,7 @@ consider creating an index or changing t
 
 <p>If this is the case, an index might need to be created, or the condition of the
query might need to be changed to take advantage of an existing index.</p>
 <p>Queries that traverse many nodes, or that read many nodes in memory, can be cancelled.
The limits can be set at runtime (also while a slow query is running) using JMX, domain &#x201c;org.apache.jackrabbit.oak&#x201d;,
type &#x201c;QueryEngineSettings&#x201d;, attribute names &#x201c;LimitInMemory&#x201d;
and &#x201c;LimitReads&#x201d;. These setting are not persisted, so in the next restart,
the default values (unlimited) are used. As a workaround, these limits can be changed using
the system properties &#x201c;oak.queryLimitInMemory&#x201d; and &#x201c;oak.queryLimitReads&#x201d;.
Queries that exceed one of the limits are cancelled with an UnsupportedOperationException
saying that &#x201c;The query read more than x nodes&#x2026; To avoid running out
of memory, processing was stopped.&#x201d;</p>
-<p>&#x201c;LimitReads&#x201d; applies to the number of nodes read by a query.
It applies whether or not an index is used. As an example, if a query has just two conditions,
as in <tt>a=1 and b=2</tt>, and if there is an index on <tt>a</tt>,
then all nodes with <tt>a=1</tt> need to be read while traversing the result.
If more nodes are read than the set limit, then an exception is thrown. If the query also
has a path condition (for example descendants of <tt>/home</tt>), and if the index
supports path conditions (which is the case for all property indexes, and also for Lucene
indexes if <tt>evaluatePathRestrictions</tt> is set), then only nodes in the given
subtree are read.</p>
+<p>&#x201c;LimitReads&#x201d; applies to the number of nodes read by a query.
It applies whether or not an index is used. The exact number of nodes read for a query depends
on many factors, mainly the query, the query plan used, the index configuration, access rights,
and nodes in the repository. The result size of a query is often much smaller than the number
of nodes read. As an example, if a query has just two conditions, as in <tt>a=1 and
b=2</tt>, and if there is an index on <tt>a</tt>, then all nodes with <tt>a=1</tt>
need to be read while traversing the result. If more nodes are read than the set limit, then
an exception is thrown. If the query also has a path condition (for example descendants of
<tt>/home</tt>), and if the index supports path conditions (which is the case
for all property indexes, and also for Lucene indexes if <tt>evaluatePathRestrictions</tt>
is set), then only nodes in the given subtree are read.</p>
 <p>&#x201c;LimitInMemory&#x201d; applies to nodes read in memory, in order
to sort the result, and in order to ensure the same node is only returned once. It applies
whether or not an index is used. As an example, if a query uses <tt>order by c</tt>,
and if the index used for this query does not support ordering by this property, then all
nodes that match the condition are read in memory first, even before the first node is returned.
Property indexed can not order, and Lucene indexes can only order when enabling <tt>ordered</tt>
for a property. Ensuring the same node is only returned once: this is needed for queries that
contain <tt>union</tt> (it is not needed when using <tt>union all</tt>).
It is also needed if a query uses <tt>or</tt> conditions on different properties.
For example, if a query uses <tt>a=1 or b=2</tt>, then the conversion to <tt>union</tt>
would be <tt>select ... where a=1 union select ... where b=2</tt>. The query is
converted to a <tt>union</tt> so that both in
 dexes can be used, in case there are separate indexes for <tt>a</tt> and <tt>b</tt>.
For XPath queries, such conversion to <tt>union</tt> is always made, and for SQL-2
queries such a conversion is only made if the <tt>union</tt> query has a lower
expected cost. When using <tt>or</tt> in combination with the same property, as
in <tt>a=1 or a=2</tt>, then no conversion to <tt>union</tt> is made.</p></div>
 <div class="section">
 <h3><a name="Full-Text_Queries"></a>Full-Text Queries</h3>
@@ -696,7 +696,7 @@ for (FacetResult.Facet facet : facets) {
 
 <div>
 <div>
-<pre class="source">SELECT [rep:facet(jcr:title)] FROM [nt:unstructured] WHERE [jcr:title]
IS NOT NULL 
+<pre class="source">SELECT [rep:facet(jcr:title)] FROM [nt:unstructured] WHERE [jcr:title]
IS NOT NULL
 </pre></div></div>
 </div>
 <div class="section">

Modified: jackrabbit/site/live/oak/docs/release-schedule.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/release-schedule.html?rev=1851606&r1=1851605&r2=1851606&view=diff
==============================================================================
--- jackrabbit/site/live/oak/docs/release-schedule.html (original)
+++ jackrabbit/site/live/oak/docs/release-schedule.html Fri Jan 18 08:02:41 2019
@@ -1,13 +1,13 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 at 2019-01-17 
+ | Generated by Apache Maven Doxia Site Renderer 1.8.1 at 2019-01-08 
  | Rendered using Apache Maven Fluido Skin 1.6
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <meta name="Date-Revision-yyyymmdd" content="20190117" />
+    <meta name="Date-Revision-yyyymmdd" content="20190108" />
     <meta http-equiv="Content-Language" content="en" />
     <title>Jackrabbit Oak &#x2013; Release Schedule</title>
     <link rel="stylesheet" href="./css/apache-maven-fluido-1.6.min.css" />
@@ -142,9 +142,9 @@
 
       <div id="breadcrumbs">
         <ul class="breadcrumb">
-        <li id="publishDate">Last Published: 2019-01-17<span class="divider">|</span>
+        <li id="publishDate">Last Published: 2019-01-08<span class="divider">|</span>
 </li>
-          <li id="projectVersion">Version: 1.12-SNAPSHOT</li>
+          <li id="projectVersion">Version: 1.10-SNAPSHOT</li>
         </ul>
       </div>
       <div class="row-fluid">
@@ -257,13 +257,12 @@
 <p>Here is the frequency where the team <b>aim</b> to cut new releases.
As we strive for quality rather than frequency the date may slip according to needs.</p>
 <ul>
 
-<li>Trunk: TBD</li>
-<li>1.10: every 4 weeks (~12 / year)</li>
-<li>1.8: every 8 weeks (~6 / year)</li>
-<li>1.6: every 13 weeks (~4 / year)</li>
-<li>1.4: every 26 weeks (~2 / year)</li>
-<li>1.2: every 52 weeks (1 / year)</li>
-<li>1.0: every 52 weeks (1 / year)</li>
+<li>Trunk: every 2 weeks (2 / month, ~26 /year)</li>
+<li>1.8: every 4 weeks (1 / month, ~12 / year)</li>
+<li>1.6: every 8 weeks (1 / other month, ~6 / year)</li>
+<li>1.4: every 13 weeks (1 / quarter, ~4 / year)</li>
+<li>1.2: every 13 weeks (1 / quarter, ~4 / year)</li>
+<li>1.0: every 26 weeks (~2 / year)</li>
 </ul>
         </div>
       </div>



Mime
View raw message