You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by th...@apache.org on 2018/03/27 08:57:18 UTC
svn commit: r1827814 -
/jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
Author: thomasm
Date: Tue Mar 27 08:57:18 2018
New Revision: 1827814
URL: http://svn.apache.org/viewvc?rev=1827814&view=rev
Log:
OAK-301 : Document Oak
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md?rev=1827814&r1=1827813&r2=1827814&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md Tue Mar 27 08:57:18 2018
@@ -437,17 +437,14 @@ excludeFromAggregation
<a name="weight"></a>
weight
-: Since 1.6.3
-: At times, we have property definitions which are added to support for dense results right out of
- the index (e.g. `contains(*, 'foo') AND [bar]='baz'`). In such cases, the added property definition "might"
- not be the best one to answer queries which only have the property restriction (eg only `[bar]='baz'`). This
- can happen when that index specifies some exclude paths and hence does not index all `bar` properties.
-
- For such cases set `weight` to `0` for such properties. In such a case IndexPlanner would not use those property
- definitions to determine if that index can answer the query but it would still use them if some other index entry
- causes that index to be selected for evaluating such a query.
-
- Refer [OAK-5899][OAK-5899] for more details
+: Allows to override the estimated number of entries per value,
+ which affects the cost of the index.
+: Since 1.6.3: if `weight` is set to `0`, then this property is assumed not to reduce the cost.
+ Queries that contain _only_ this condition should not use that index.
+ See [OAK-5899][OAK-5899] for details.
+: Since 1.7.11: if `weight` is set to `10`, then the estimated number of unique entries is 10.
+ This means, the cost is reduced by a factor of about 10, for queries that contain this condition.
+ See [OAK-6735][OAK-6735] for details.
<a name="property-names"></a>**Property Names**