You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/05/27 10:50:00 UTC
[jira] [Commented] (OAK-4007) "reset clusterId tool" in oak-run
[ https://issues.apache.org/jira/browse/OAK-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848827#comment-16848827 ]
Julian Reschke commented on OAK-4007:
-------------------------------------
[~egli], [~mreutegg] - while updating docs for oak-run I came across this one, supporting DocumentMK on MongoDB but not RDB. Is that an oversight? (If so, I'll add that).
> "reset clusterId tool" in oak-run
> ---------------------------------
>
> Key: OAK-4007
> URL: https://issues.apache.org/jira/browse/OAK-4007
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Affects Versions: 1.3.15
> Reporter: Stefan Egli
> Assignee: Amit Jain
> Priority: Blocker
> Fix For: 1.2.12, 1.3.16, 1.4
>
> Attachments: OAK-4007.1.2.branch.patch.v1.txt, OAK-4007.patch.v1.txt
>
>
> There should be a tool in oak-run that allows to reset the clusterId as defined and described in OAK-4006 (the hidden /:clusterConfig/:clusterId property). As suggested by [~catholicon] on the oak-dev list it should be possible to reset the clusterId such that it is null (so that it would support easy multi-cloning cases).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)