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

Andrei Dulceanu updated OAK-8828:
---------------------------------
    Description: 
We need the ability to configure the maximum number of journal entries (i.e. 
revisions) to be copied by {{oak-run segment-copy}}. This way we can void 
timeout issues when transferring a large journal over the network with the sole 
purpose to compact the repository.

For this we can add a new optional argument {{--last <REV_COUNT>}}, with the 
same semantics as {{oak-run check}}. If the argument is used, but a specific 
number of revisions is not specified, the tool will copy by default only the 
last revision.

  was:
We need the ability to configure the maximum number of journal entries (i.e. 
revisions) to be copied by {{oak-run segment-copy}}. This way we can void 
timeout issues when transferring a large journal over the network with the sole 
purpose to compact the repository.

For this we can add a new optional argument {{--last <REV_COUNT>}}, with the 
same semantics as {{oak-run check}}. If the argument is used, but a specific 
number of revisions is not specified, the tool will check by default only the 
last revision.


> Configure the maximum number of journal entries to be copied with segment-copy
> ------------------------------------------------------------------------------
>
>                 Key: OAK-8828
>                 URL: https://issues.apache.org/jira/browse/OAK-8828
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-azure, segment-tar
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>
> We need the ability to configure the maximum number of journal entries (i.e. 
> revisions) to be copied by {{oak-run segment-copy}}. This way we can void 
> timeout issues when transferring a large journal over the network with the 
> sole purpose to compact the repository.
> For this we can add a new optional argument {{--last <REV_COUNT>}}, with the 
> same semantics as {{oak-run check}}. If the argument is used, but a specific 
> number of revisions is not specified, the tool will copy by default only the 
> last revision.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to