[
https://issues.apache.org/jira/browse/OAK-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101422#comment-16101422
]
Chetan Mehrotra edited comment on OAK-6497 at 7/26/17 9:25 AM:
---------------------------------------------------------------
[~frm] [~mduerig] One possible approach I was think was to have a
NodeStoreFixtureProvider support for old segment module by adding an explicit
dependency to oak-segment 1.6.3. We can keep this for one release and then
remove this support later.
This would allow for example to use oak-run-1.7.5 for old setups with whatever
features implemented by now. Would come up with a patch to see if this is
feasible
was (Author: chetanm):
[~frm] [~mduerig] One possible approach I was think was to have a
NodeStoreFixtureProvider support for old segment module by adding an explicit
dependency to oak-segment 1.6.3. We can keep this for one release and then
remove this support later.
This would allow for example to use oak-run-1.7.5 for old setups with whatever
features implemented by now
> Support old Segment NodeStore setups for oak-run index tooling
> --------------------------------------------------------------
>
> Key: OAK-6497
> URL: https://issues.apache.org/jira/browse/OAK-6497
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> oak-run index command has been introduced in trunk and can be used in read
> only mode against existing setups. This would work fine for all
> DocumentNodeStore setups. However would not work SegmentNodeStore setups <=
> Oak 1.4
> This task is meant to figure out possible approaches for enabling such a
> support for oak-run builds from trunk
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
