Hi, Could we use a new index type for the new format? For example "ordered2" instead of "ordered". I know not very creative naming :-)
I would prefer if the translation is done automatically on restart or re-index. I woudn't want to install Groovy and / or have to do manual steps if possible. Regards, Thomas On 27/08/14 15:02, "Davide Giannella" <[email protected]> wrote: >Hello team, > >as already tracked in https://issues.apache.org/jira/browse/OAK-1763 the >ordered index does not comply to JCR's semantics. > >We start seeing issues in (pre)production around it and therefore I >think we need a fix. > >Unfortunately with the changes of the encoding and algorithm any >existing ordered index will have to be "translated" into the new encoding. > >I thought therefore that in case of big indexes/repos it would be faster >if instead of issuing a reindex having a groovy script (oak-console) >that applies the "translation" to the already indexed structure. To be >run with a repository shutdown. > >The steps of the script would be something on the line of: walk the >list, take the current key and properties (node) "tranlate" into new >encoding, save, move to the next node. > >Thoughts? Otherwise I'll add a note in the ticket itself for not loosing >track. > >Cheers >Davide > >
