Skip to content

Gracefully drop Bitset encoding attempt if offset different too large - #39

Merged
Antony Stubbs (astubbs) merged 4 commits into
confluentinc:0.2.0.xfrom
astubbs:bug/drop-bitset
Nov 30, 2020
Merged

Antony Stubbs (astubbs) merged 4 commits into
confluentinc:0.2.0.xfrom
astubbs:bug/drop-bitset

Conversation

@astubbs

@astubbs Antony Stubbs (astubbs) commented Nov 29, 2020 •

Copy link
Copy Markdown
Contributor

Fixes #35
Will be improved with #37

@astubbs
Antony Stubbs (astubbs) changed the base branch from master to 0.2.0.x November 29, 2020 12:53
@astubbs
Antony Stubbs (astubbs) force-pushed the bug/drop-bitset branch 2 times, most recently from d0993f1 to 5e0436b Compare November 30, 2020 16:28
@astubbs
Antony Stubbs (astubbs) force-pushed the bug/drop-bitset branch 2 times, most recently from c21a278 to 8841933 Compare November 30, 2020 19:32
…short range)

RunLength encoding will still be used.

See #37 Support BitSet encoding lengths longer than Short.MAX_VALUE
confluentinc#37

A test did try to cover this, but the offset difference wasn't large enough.
…ode drop if too big

Test now exercises the metadata stripping flow.
Capture issue with run length encoding - short cast.
@astubbs
Antony Stubbs (astubbs) merged commit 0dcda6a into confluentinc:0.2.0.x Nov 30, 2020
@astubbs
Antony Stubbs (astubbs) deleted the bug/drop-bitset branch November 30, 2020 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RuntimeException when running with very high options in 0.2.0.0 (Bitset too long to encode)

1 participant