gchq
Add a range-lookup() XSLT function
Currently the lookup() function will assume the passed key is a string value to lookup in the key/value store. If it can't find it it then tries to convert the key into a long and if that works does a lookup in the range store.
For use cases where the person writing the XSLT (that uses the lookup) knows the data is all range keys it would be more performant to have a range-lookup() function that went directly to the range store.
lookup() could still be used for cased where the type of key in the store is unknown.
It could be argued that lookup should only lookup in the kv store to avoid the additional lookup in the range store (if the key is a long), but changing the behaviour would impact existing uses of the lookup function.
Another option would be to add a new overloaded arg to specify the mode, auto|key|range, auto behaves as currently, key just does and key lookup and range converts to long and does a range lookup.