Description
This class exposes a bunch of new capabilities, but they aren't adequately documented. In order to make use of the skipper, you need a mental model of the skip list data structure and the implicit assumptions that are being made by this class. Some things I found out that weren't clear at first:
- Level 0 is the "top" level with the largest blocks; higher numbered levels represent successively nested sub-blocks.
- The skipper only really works with fields that are primary index sort keys (I think?). What happens if you try to use the skipper with non-sorted fields? Can you still read block level statistics? Maybe - but how does skipping function in that case?
- advance(docId) is forward-only, but what are the expectations around
advance(minValue, maxValue)? Is it possible to reverse using this API?
I can try to improve the docs, but my understanding is only superficial, and I don't want to add to the confusion, so for now I'm just asking questions :)
Description
This class exposes a bunch of new capabilities, but they aren't adequately documented. In order to make use of the skipper, you need a mental model of the skip list data structure and the implicit assumptions that are being made by this class. Some things I found out that weren't clear at first:
advance(minValue, maxValue)? Is it possible to reverse using this API?I can try to improve the docs, but my understanding is only superficial, and I don't want to add to the confusion, so for now I'm just asking questions :)