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

Alex Parvulescu updated OAK-4043:
---------------------------------
    Attachment: OAK-4043.patch

proposed patch. [~chetanm] please review, especially the documentmk parts.

I kept the existing naming convention. {{name.endsWith("async") && 
ps.getType().equals(Type.STRING)}} should cover all existing values, plus one 
can add anything ending in 'async' and it will be considered a reference.

> 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: Alex Parvulescu
>            Priority: Blocker
>              Labels: candidate_oak_1_4
>             Fix For: 1.6, 1.5.11
>
>         Attachments: OAK-4043.patch
>
>
> 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)

Reply via email to