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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/02/24 10:22:18 UTC
[jira] [Commented] (OAK-4043) Oak run checkpoints needs to account
for multiple index lanes
[ https://issues.apache.org/jira/browse/OAK-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162718#comment-15162718 ]
Davide Giannella commented on OAK-4043:
---------------------------------------
1.3.17 will be the last unstable cut that will then be the same as 1.4.0 and branch. Added such revision.
> 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
> Priority: Blocker
> Fix For: 1.4, 1.3.17
>
>
> 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)