Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 4 commits into from
Nov 30, 2020

Conversation

astubbs
Copy link
Contributor

@astubbs astubbs commented Nov 29, 2020

Fixes #35
Will be improved with #37

@astubbs astubbs changed the base branch from master to 0.2.0.x November 29, 2020 12:53
@astubbs astubbs force-pushed the bug/drop-bitset branch 2 times, most recently from d0993f1 to 5e0436b Compare November 30, 2020 16:28
@astubbs 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 confluentinc#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 astubbs merged commit 0dcda6a into confluentinc:0.2.0.x Nov 30, 2020
@astubbs 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