Repository navigation
Support BitSet and RunLength encoding lengths longer than Short.MAX_VALUE #37
Description
BitSet offset encodings are limited to Short.MAX_VALUE (32,000~ relative offsets) because a Short is used to serialise the Bitset run length. In order to support longer BitSets, need to use a bigger format like Integer (2,147,483,647 relative offsets).
RunLength has a similar problem - an integer is silently cast to a short, assuming a given run length is less than 32,000. Which may not always be the case. A new version of run length could use integer's instead. Could be another encoder that runs in parallel...
Activity
bug: Revert 281f5fc fix: Turn off bitset length fatal check
astubbs commentedon Nov 27, 2020
Not as important if #38 is fixed
bug: Revert 281f5fc fix: Turn off bitset length fatal check
Gracefully drop bitset encoding if offset difference too large
Gracefully drop bitset encoding if offset difference too large
Gracefully drop bitset encoding if offset difference too large
fix: Gracefully drop Bitset encoding if offset difference too large (…
fix: Gracefully drop Bitset encoding if offset difference too large (…
[-]Support BitSet encoding lengths longer than Short.MAX_VALUE[/-][+]Support BitSet and RunLength encoding lengths longer than Short.MAX_VALUE[/+]fix: Gracefully drop Bitset encoding if offset difference too large (…
fix: Gracefully drop Bitset encoding if offset difference too large (…
fix: Gracefully drop Bitset encoding if offset difference too large (…
feature: #37 Adds support for larger bitset and run-length encodings
feature: #37 Adds support for larger bitset and run-length encodings