[
https://issues.apache.org/jira/browse/OAK-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973341#comment-13973341
]
Jukka Zitting commented on OAK-1462:
------------------------------------
Do we need the aggregate index to be a separate service from the plain Lucene
index? It seems like a simpler approach would be to just merge the
functionality into the Lucene index.
> Aggregate Index isn't usable in an osgi environment
> ---------------------------------------------------
>
> Key: OAK-1462
> URL: https://issues.apache.org/jira/browse/OAK-1462
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, query
> Reporter: Alex Parvulescu
> Assignee: Chetan Mehrotra
> Fix For: 1.1
>
>
> There are a few issues with the Aggregate Index in an osgi env.
> - First the cost is the same as the wrapped index. This is not really about
> osgi, but the fact that in an osgi enabled environment there will be 2
> indices returning the same cost (ex. lucene and aggregate lucene) so some
> full-text queries may fail randomly.
> - Second, there are no osgi annotations on the Aggregate Index so it is not
> automatically enabled. I'm not sure how to enable that yet.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
