[ 
https://issues.apache.org/jira/browse/OAK-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294784#comment-16294784
 ] 

Michael Dürig edited comment on OAK-6625 at 12/18/17 10:47 AM:
---------------------------------------------------------------

Re. 
https://issues.apache.org/jira/browse/OAK-3855?focusedCommentId=16294770&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16294770:
 No {{-force}} is not yet mentioned in {{oak-doc}}. I'll fix this.

See OAK-7075.


was (Author: mduerig):
Re. 
https://issues.apache.org/jira/browse/OAK-3855?focusedCommentId=16294770&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16294770:
 No {{-force}} is not yet mentioned in {{oak-doc}}. I'll fix this.

> Avoid oak-run compact inadvertently upgrading the segment format 
> -----------------------------------------------------------------
>
>                 Key: OAK-6625
>                 URL: https://issues.apache.org/jira/browse/OAK-6625
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run, segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: gc, production, resilience
>             Fix For: 1.7.7, 1.8
>
>
> The transparent upgrade feature for segments from version 12 to 13 should not 
> cause "accidental upgrades". That is, running Oak 1.8 oak-run compact on a 
> store with segment version 12 should bail out unless a special option was 
> specified on the command line. 



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

Reply via email to