Thanks Tomek for confirmation. Opened OAK-4684 to track that Chetan Mehrotra
On Fri, Aug 19, 2016 at 3:52 PM, Tomek Rekawek <reka...@adobe.com> wrote: > Hi Chetan, > > yes, it seems that this has been overlooked in the OAK-3239 (porting the > —include-paths support from RepositoryUpgrade). Feel free to create an issue > / commit a patch or let me know if you want me to do it. > > Best regards, > Tomek > > -- > Tomek Rękawek | Adobe Research | www.adobe.com > reka...@adobe.com > >> On 19 Aug 2016, at 10:38, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: >> >> For complete migration yes all bits are there. However people also use >> this for partial incremental migration from source system to target >> system. In that case include paths are provide for those paths whose >> content need to be updated. In such a case it can happen that derived >> content for those paths (property index, permission store entries) do >> not get updated and that would result in inconsistent state >> Chetan Mehrotra >> >> >> On Fri, Aug 19, 2016 at 1:59 PM, Alex Parvulescu >> <alex.parvule...@gmail.com> wrote: >>> Hi, >>> >>> I don't think any extra hooks are needed here. Sidegrade is just a change >>> in persistence format, all the bits should be there already in the old >>> repository. >>> >>> best, >>> alex >>> >>> On Fri, Aug 19, 2016 at 6:45 AM, Chetan Mehrotra <chetan.mehro...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Does RepositorySidegrade runs all the commit hooks required for >>>> getting a consistent JCR level state like permission editor, property >>>> editor etc >>>> >>>> I can such hooks configured for RepositoryUpgrade but not seeing any >>>> such hook configured for RepositorySidegrade >>>> >>>> Probably we should also configure same set of hooks? >>>> >>>> Chetan Mehrotra >>>> >
