Re: [Exist-development] Legacy Range Index plans?

[<wol...@ex...>]

> 1) Remove it after 2.2 release?

We need to give users some time to update their index definitions, so we have to keep the old index for a while. As we did for the legacy full-text index, I would suggest to disable the legacy range index in the default configuration after 2.2 has been released and then remove it entirely in 2.3.

There’s also some work to do: 1) @xml:id are still using the legacy range index, 2) fn:matches is not supported due to regex limitations in lucence. Both issues need to be addressed before we disable the old index.

I agree the legacy range index is polluting NativeBroker with lots of nasty code, which can be removed once we drop the index.

Wolfgang