[
https://issues.apache.org/jira/browse/OAK-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved OAK-4490.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.5.5
Committed a bit modified approach which exposes the SegmentNodeStore via a
{{NodeStoreProvider}}.
*Usage*
Configure the SegmentNodeStore service as
{noformat}
secondary=true
{noformat}
In this mode SegmentNodeStoreService would wait for a BlobStore reference
(customBlobStore would be assumed to be true) and later it would register an
instance of {{NodeStoreProvider}} with {{role}} service property set to
{{secondary}}
Done changes in both oak-segment and oak-segment-tar
> 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, 1.5.5, 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)
