[ https://issues.apache.org/jira/browse/OAK-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189192#comment-16189192 ]
Vikas Saurabh commented on OAK-6535: ------------------------------------ [~chetanm], reviewed modified files (added are left). A few notes: {noformat} LIPService.java + tracker = new IndexTracker(); {noformat} Do we require CoR for mounted stores and nrt? Maybe, I missed it somewhere...: * it seems we don't plan with prop idx when sort order is defined - that can be confusing... maybe a WARN?? ("warn", because it seems to me that query and def aren't in sync with each other) * I can't see how are we skipping over prox idx in presence of a full text clause (also, we should warn if/when we skip prop idx iteration) > Synchronous Lucene Property Indexes > ----------------------------------- > > Key: OAK-6535 > URL: https://issues.apache.org/jira/browse/OAK-6535 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: lucene, property-index > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6535-v1.diff > > > Oak 1.6 added support for Lucene Hybrid Index (OAK-4412). That enables near > real time (NRT) support for Lucene based indexes. It also had a limited > support for sync indexes. This feature aims to improve that to next level and > enable support for sync property indexes. > More details at > https://wiki.apache.org/jackrabbit/Synchronous%20Lucene%20Property%20Indexes -- This message was sent by Atlassian JIRA (v6.4.14#64029)