Hi,

>>Could we use a new index type for the new format? For example "ordered2"
>> instead of "ordered". I know not very creative naming :-)
>This is a fix to the current index implementation. I think we should
>stay with the current index.

Well, we need some way to know whether the data was migrated or not. It
could be a separate property, for example "formatVersion". It doesn't need
to be a new index type.

>> 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.
>>
>A normal reindex would suffice for the vast majority of cases. We have
>some edge ones however that takes days to complete a reindex.

If it takes days to complete a re-index, then it sounds like something is
broken, and that needs to be investigated. Re-indexing at most scans the
whole repository, so it should not take days, except maybe for a
multi-billion-nodes repository. I guess that's not the case here.

>The groovy script is just a way to speed it up in these edge cases. You
>don't need to install anything as the oak-console can already execute
>groovy scripts.

OK, but no manual steps should not be needed for a regular software
upgrade.

Regards,
Thomas

Reply via email to