[Exist-development] Legacy Range Index plans?

[Adam R. <ad...@ex...>]

Hi there,

I am just wondering what the plan is for the NativeValueIndex (i.e.
legacy range index) in eXist. I am wondering if the plan is either:

1) Remove it after 2.2 release?

2) Migrate it to fit entirely into the newer indexing pipeline format,
cleaning up NativeBroker#endElement. And if so, what is the perceived
value in keeping the legacy range index?

3) Something else?

I notice that it does some quite nasty dirty reads against the dom.dbx
before the transaction that represents that data is actually committed
- see the calls to getNodeValue in NativeBroker#endElement. I would
like to eliminate that sort of behaviour.

Cheers Adam.

-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb