[
https://issues.apache.org/jira/browse/OAK-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966883#comment-13966883
]
Jukka Zitting commented on OAK-1722:
------------------------------------
See
https://github.com/jukka/jackrabbit-oak/commit/f0c76b4e2efd7d5f30115620a32d9b5e0e8d0880
for a quick draft of how we could use the {{Observer}} mechanism to keep a
shared {{IndexSearcher}} instance up to date with changes in the repository.
> Use a shared IndexSearcher for performing Lucene queries
> --------------------------------------------------------
>
> Key: OAK-1722
> URL: https://issues.apache.org/jira/browse/OAK-1722
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.0, 1.1
>
>
> Currently the Lucene integrations opens a new IndexSeracher for every read
> call. This proves to be costly as per OAK-1702. Instead we should use a
> shared IndexSearcher based on approach taken in Lucene
> [SearcherManager|https://lucene.apache.org/core/3_6_0/api/all/org/apache/lucene/search/SearcherManager.html].
> Further there needs to be a way to pickup any changes in Lucene index across
> cluster nodes
--
This message was sent by Atlassian JIRA
(v6.2#6252)
