[
https://issues.apache.org/jira/browse/OAK-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495519#comment-15495519
]
Chetan Mehrotra edited comment on OAK-4043 at 9/16/16 6:23 AM:
---
I would prefer to avoid any change in existing names. Probably we can follow
the convention of such names having prefix of {{async}} (possibly add a check
in Oak also to enforce that) and then figure out the list of checkpoints based
on that.
Or you can possibly consider any string property in {{:async}} to be a possible
checkpoint to determine match!
Given the impact of this issue marking this as blocker for next dot release
was (Author: chetanm):
I would prefer to avoid any change in existing names. Probably we can follow
the convention of such names having prefix of {{async}} (possibly add a check
in Oak also to enforce that) and then figure out the list of checkpoints based
on that.
Or you can possibly consider any string property in {{:async}} to be a possible
checkpoint to determine match!
> Oak run checkpoints needs to account for multiple index lanes
> -
>
> Key: OAK-4043
> URL: https://issues.apache.org/jira/browse/OAK-4043
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, run
>Reporter: Alex Parvulescu
>Assignee: Davide Giannella
>Priority: Blocker
> Labels: candidate_oak_1_4
> Fix For: 1.6, 1.5.11
>
>
> Oak run {{checkpoints rm-unreferenced}} [0] currently is hardcoded on a
> single checkpoint reference (the default one). Now is it possible to add
> multiple lanes, which we already did in AEM, but the checkpoint tool is
> blissfully unaware of this and it might trigger a full reindex following
> offline compaction.
> This needs fixing before the big 1.4 release, so I'm marking it as a blocker.
> fyi [~edivad], [~chetanm]
> [0] https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run#checkpoints
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
