Revert "Build: Bump roaringbitmap from 1.3.0 to 1.6.0 (#14991)"#15358
Merged
nastra merged 1 commit intoapache:mainfrom Feb 19, 2026
Merged
Revert "Build: Bump roaringbitmap from 1.3.0 to 1.6.0 (#14991)"#15358nastra merged 1 commit intoapache:mainfrom
nastra merged 1 commit intoapache:mainfrom
Conversation
This reverts commit 8967729.
singhpk234
approved these changes
Feb 18, 2026
huaxingao
approved these changes
Feb 18, 2026
kevinjqliu
approved these changes
Feb 18, 2026
Member
|
@amogh-jahagirdar could you please create an issue to track? We need to make a decision for spark 4.2 integration. |
manuzhang
approved these changes
Feb 18, 2026
dramaticlly
approved these changes
Feb 19, 2026
ebyhr
approved these changes
Feb 19, 2026
nastra
approved these changes
Feb 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts commit 8967729.
As discussed in community sync for the 1.11 release, we'll revert this set of changes since there are challenges for downstream consumers and the jitpack repo. Some form of the original change may be inevitable for future spark integrations, but at least for the current release it shouldn't be required. Long term, we can work with RoaringBitmap maintainers to try and get the newer versions onto maven central or we may have to find alternative mechanisms like shading (not preferable).