[
https://issues.apache.org/jira/browse/OAK-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347979#comment-15347979
]
Chetan Mehrotra commented on OAK-4490:
--------------------------------------
Based on [discussion on
dl|http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201606.mbox/%3cCAHCW-mktC6cjNHBnaPo=fpott6dhz9aosh8ogeivojftuzj...@mail.gmail.com%3e]
would change the approach to use the SecondaryNodeStore interface (OAK-4369).
Would come up with update patch
> Expose SegmentNodeStore as a secondary NodeStore
> ------------------------------------------------
>
> Key: OAK-4490
> URL: https://issues.apache.org/jira/browse/OAK-4490
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar, segmentmk
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.6, Segment Tar 0.0.4
>
> Attachments: OAK-4490-v1.patch
>
>
> For OAK-4180 to work we would need to configure a SegmentNodeStore as a
> secondary NodeStore. This NodeStore instance is used as a local cache of
> remote content for certain paths.
> Point to note
> # The NodeStore instance would be full functional except it would not be
> registering any Observor
> # With this its possible to have a setup where multiple NodeStore instances
> are registered in same service registry. So it needs to be ensure that any
> other component which depends on NodeStore binds to correct store
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)