[
https://issues.apache.org/jira/browse/OAK-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070976#comment-15070976
]
Vikas Saurabh edited comment on OAK-3826 at 12/24/15 1:10 PM:
--------------------------------------------------------------
Attaching [patch|^OAK-3826.patch] which assumes OAK-3815 is resolved using
[OAK-3815-v1-1.patch|https://issues.apache.org/jira/secure/attachment/12778789/OAK-3815-v1.patch]
attached in that issue. The patch removes bind/unbind based refresh from
LuceneIndexProviderService and the test cases are adjusted accordingly.
was (Author: catholicon):
Attaching [patch|^OAK-3826.patch] which assumes OAK-3815 is resolved using
[OAK-3815-v1-1.patch|^https://issues.apache.org/jira/secure/attachment/12778789/OAK-3815-v1.patch]
attached in that issue. The patch removes bind/unbind based refresh from
LuceneIndexProviderService and the test cases are adjusted accordingly.
> Lucene index augmentation doesn't work in Osgi environment
> ----------------------------------------------------------
>
> Key: OAK-3826
> URL: https://issues.apache.org/jira/browse/OAK-3826
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.4
>
> Attachments: OAK-3826.patch
>
>
> OAK-3576 introduced a way to hook SPI to provide extra fields and query terms
> for a lucene index.
> In Osgi world, due to OAK-3815, {{LuceneIndexProviderService}} registered
> references to SPI and pinged {{IndexAugmentFactory}} to update its map. But,
> it seems bind/unbind methods get called ahead of time as compared to the
> information Tracker contains. This leads to wrong set of services captured by
> {{IndexAugmentFactory}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
