[jackrabbit-oak] 01/01: OAK-8910 Improve OAK Lucene Index Documentation

[th...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

thomasm pushed a commit to branch OAK-8910
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git

commit c95234e24310f376636b6b53d877fd896fb200dc
Author: thomasm <th...@apache.org>
AuthorDate: Wed Jul 7 15:36:27 2021 +0200

    OAK-8910 Improve OAK Lucene Index Documentation
---
 oak-doc/src/site/markdown/query/lucene.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/oak-doc/src/site/markdown/query/lucene.md b/oak-doc/src/site/markdown/query/lucene.md
index 95b709e..f26d7cd 100644
--- a/oak-doc/src/site/markdown/query/lucene.md
+++ b/oak-doc/src/site/markdown/query/lucene.md
@@ -434,6 +434,18 @@ ordered
   only supported for single value property. Enabling this on multi value property
   would cause indexing to fail.
 
+  Ordering is supported on properties, and on functions. To order on the name of the node,
+  use the following query and index definition:
+
+    SELECT * FROM [sling:Folder] WHERE ISCHILDNODE('/content') ORDER BY NAME()
+    
+    + sling:Folder
+      + properties (nt:unstructured)
+        + nodeName (nt:unstructured)
+          - function (string) = 'name()'
+          - propertyIndex (boolean) = true
+          - ordered (boolean) = true
+  
 type
 : JCR Property type. Can be one of `Date`, `Boolean`, `Double` , `String`, `Long`, or `Binary`. 
   Mostly inferred from the indexed value. However in some cases where same property