[
https://issues.apache.org/jira/browse/OAK-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189546#comment-16189546
]
Chetan Mehrotra commented on OAK-6535:
--------------------------------------
There is a potential issue for the initial setup. AsyncIndexUpdate would fail
with merge exception for the first run because two tasks collide
# IndexUpdate (as part of AsyncIndexUpdate) - Removing all hidden nodes for any
index which needs to be reindexed and which would be the case for any lucene
index on first start
# Hybrid PropertyIndexUpdate - This would add nodes as hidden nodes prior to
first reindex
Due to above 2 first commit fails with deletedChangedNode exception. So we
would need a way for IndexUpdate to ignore removing such property index nodes
for the reindex case. This can possibly be done via adding some convention i.e.
presence of some property on the hidden node ":property-index"
However we would still need to provide a way to properly clean the
":property-index" for cases where index definition got changed but empty head
buckets for properties which were earlier indexer were still present
[~catholicon] Thoughts?
> 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)
