jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4043) Oak run checkpoints needs to account for multiple index lanes
Date Fri, 16 Sep 2016 06:21:20 GMT

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

Chetan Mehrotra commented on OAK-4043:

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: Critical
>              Labels: candidate_oak_1_4
>             Fix For: 1.6
> 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

View raw message