[
https://issues.apache.org/jira/browse/OAK-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969435#comment-13969435
]
Chetan Mehrotra commented on OAK-1724:
--------------------------------------
Hit a bummer here ... The whole idea of copying the updated binaries to local
file system relied on the fact that Lucene index files are not modified once
created. And looks like that is not the case. So its not safe to copy the files
when existing files (with same name) are already in use
So now I think we need to go for OAK-1726 for making Lucene work better on FDS
> Enable copying of Lucene index to local file system for read queries
> --------------------------------------------------------------------
>
> Key: OAK-1724
> URL: https://issues.apache.org/jira/browse/OAK-1724
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.0, 1.1
>
>
> Currently the Lucene index is stored in NodeStore and is accessed via
> OakDirectory which is an implementation of [Lucene
> Directory|https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/store/Directory.html].
> This would work fine for SegmentStore but does not work very well when
> BlobStore is used as with DocumentNodeStore
> For such scenarios it should be possible to copy the Lucene index to local
> file system and then read queries are performed using that. IndexWriter would
> continue to use the OakDirectory to store the updated index content in
> NodeStore.
> As Lucene does not modify any index file once created (ther are either
> deleted or new one created), it should be possible to incrementally update
> the index by copying newly created segment files.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
