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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/11/21 09:08:00 UTC

[jira] [Updated] (OAK-6190) Allow to migrate checkpoints even if the custom include paths are specified

     [ https://issues.apache.org/jira/browse/OAK-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek updated OAK-6190:
-------------------------------
    Fix Version/s: 1.6.7

> Allow to migrate checkpoints even if the custom include paths are specified
> ---------------------------------------------------------------------------
>
>                 Key: OAK-6190
>                 URL: https://issues.apache.org/jira/browse/OAK-6190
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>            Reporter: Tomek Rękawek
>             Fix For: 1.7.0, 1.8, 1.6.7
>
>
> Right now, the checkpoints are not migrated if the {{\-\-include,exclude,merge\-paths}} option is specified. Let's add a new parameter: {{\-\-force\-checkpoints}} to force the checkpoint migration in such cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)