amit-jain commented on code in PR #2817:
URL: https://github.com/apache/jackrabbit-oak/pull/2817#discussion_r3921585720


##########
oak-search-lucene-ng/README.md:
##########
@@ -0,0 +1,109 @@
+# oak-search-lucene-ng
+
+Lucene 9 index provider for Oak (`type="lucene9"`).
+
+## Feature parity
+
+| Feature | Legacy Lucene | Elastic | LuceneNg |
+|---|---|---|---|
+| Property restrictions, path/type filters | ✓ | ✓ | ✓ |
+| Fulltext search | ✓ | ✓ | ✓ |
+| Index-time aggregation | ✓ | ✓ | ✓ |
+| Facets (insecure / statistical / secure) | ✓ | ✓ | ✓ |
+| Excerpts | ✓ | ✓ | ✓ |
+| Ordering / sorting | ✓ | ✓ | ✓ |
+| Suggestions | ✓ | ✓ | ✗ |
+| Spellcheck | ✓ | ✓ | ✗ |
+| Similarity / More Like This | ✓ | ✓ (+ KNN) | ✗ |
+| Native queries | ✓ | ✓ | ✗ |
+| Index statistics / JMX | ✓ | ✓ | ✗ |
+| Index augmentors [^1] | ✓ | ✗ | ✗ |
+| NRT / hybrid indexing | ✓ | ✗ | ✗ |
+| Index copier (CopyOnRead/Write) | ✓ | ✗ | ✗ |

Review Comment:
   This shuold be a required feature to add and not just good to have. Without 
this, the luceneNG index will not work in downstream applications. The reads 
from remote blob stores will trigger the readiness probes (on k8s specifically) 
and likely take a very long time for pods to start.
   
   This was added after oberserving such problems in production and nothing in 
lucene9  imo ameliorates that problem. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to