[
https://issues.apache.org/jira/browse/OAK-8703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956126#comment-16956126
]
Andrei Dulceanu commented on OAK-8703:
--------------------------------------
[~ierandra], applying the patch fails for me because of this line in the patch:
{noformat}
can't find file to patch at input line 8
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index:
jackrabbit-oak/oak-run/src/main/java/org/apache/jackrabbit/oak/run/CheckCommand.java
|IDEA additional info:
|Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
|<+>UTF-8
{noformat}
Can you please use this command when creating the patch: {{git diff --no-prefix
upstream-trunk > your-patch.patch}}?
> Configure the maximum number of revisions to be checked by consistency check
> ----------------------------------------------------------------------------
>
> Key: OAK-8703
> URL: https://issues.apache.org/jira/browse/OAK-8703
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-run, segment-tar
> Reporter: Ieran Draghiciu
> Assignee: Andrei Dulceanu
> Priority: Major
> Attachments: OAK-8703-02.patch, OAK-8703.patch
>
>
> We need the ability to configure the maximum number of revisions to be
> checked by {{oak-run check}}. This way we can quickly tell whether there's a
> valid revision in the last {{n}} revisions. Moreover, this comes handy when
> we want to test only the last revision (current head state) of the repository.
> For this we can add a new optional argument {{--maxRevisionsToCheck}}. If the
> argument is used, but a specific number of revisions is not specified, the
> tool will check by default only the last revision.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
