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 ca...@apache.org on 2016/02/10 14:58:21 UTC

svn commit: r1729600 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md

Author: catholicon
Date: Wed Feb 10 13:58:21 2016
New Revision: 1729600

URL: http://svn.apache.org/viewvc?rev=1729600&view=rev
Log:
OAK-3973: There should be a way to get filtered suggestions based on some path

Update documentation on how to use descendant contraint and limitations (just OAK-3394 works)

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=1729600&r1=1729599&r2=1729600&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 Wed Feb 10 13:58:21 2016
@@ -1003,6 +1003,18 @@ supported for backward compatibility, bu
 Setting up `useInSuggest=true` for a property definition having `name=:nodeName` would add node names to
 suggestion dictionary (See [property name](#property-names) for node name indexing)
 
+Since, Oak 1.3.16, very little support exists for queries with `ISDESCENDANTNODE` constraint to subset suggestions
+on a sub-tree.  It requires `evaluatePathRestrictions=true` on index definition. e.g.
+```
+SELECT rep:suggest() FROM [nt:base] WHERE SUGGEST('test') AND ISDESCENDANTNODE('/a/b')
+```
+or
+```
+/jcr:root/a/b//[rep:suggest('in 201')]/(rep:suggest())
+```
+Note, the subset is done by filtering top 10 suggestions. So, it's possible to get no suggestions for a subtree query,
+if top 10 suggestions are not part of that subtree. For details look at [OAK-3994] and related issues.
+
 #### Spellchecking
 
 `@since Oak 1.1.17, 1.0.13`
@@ -1035,6 +1047,17 @@ Since Oak 1.3.11, the each suggestion wo
           - useInSpellcheck = true
 ```
 
+Since, Oak 1.3.16, very little support exists for queries with `ISDESCENDANTNODE` constraint to subset suggestions
+on a sub-tree. It requires `evaluatePathRestrictions=true` on index definition. e.g.
+```
+SELECT rep:suggest() FROM [nt:base] WHERE SUGGEST('test') AND ISDESCENDANTNODE('/a/b')
+```
+or
+```
+/jcr:root/a/b//[rep:suggest('in 201')]/(rep:suggest())
+```
+Note, the subset is done by filtering top 10 spellchecks. So, it's possible to get no results for a subtree query,
+if top 10 spellchecks are not part of that subtree. For details look at [OAK-3994] and related issues.
 
 #### Facets
 
@@ -1507,6 +1530,7 @@ such fields
 [OAK-2853]: https://issues.apache.org/jira/browse/OAK-2853
 [OAK-2892]: https://issues.apache.org/jira/browse/OAK-2892
 [OAK-3367]: https://issues.apache.org/jira/browse/OAK-3367
+[OAK-3994]: https://issues.apache.org/jira/browse/OAK-3394
 [luke]: https://code.google.com/p/luke/
 [tika]: http://tika.apache.org/
 [oak-console]: https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run#console