[BUILD] Upgrade RoaringBitmap to 1.5.2#49710
[BUILD] Upgrade RoaringBitmap to 1.5.2#49710LuciferYang wants to merge 10 commits intoapache:masterfrom
RoaringBitmap to 1.5.2#49710Conversation
| <enabled>false</enabled> | ||
| </snapshots> | ||
| </repository> | ||
| <repository> |
There was a problem hiding this comment.
The new version of RoaringBitmap requires configuring additional repositories:
The second method requires additional configuration of a GitHub token, so Method One was chosen here.
LuciferYang
force-pushed
the
r-map-1.3.19
branch
from
09ffeb7 to
34d60a9
Compare
| required: false | ||
| type: string | ||
| default: 17 | ||
| default: 21 |
There was a problem hiding this comment.
will revert after test
|
Here is a discussion about republishing to Maven Central： but it seems unclear when it will be republished to Maven Central instead of just JitPack and GitHub packages. We also have the option to wait for the republish of |
| <dependency> | ||
| <groupId>org.roaringbitmap</groupId> | ||
| <artifactId>RoaringBitmap</artifactId> | ||
| <groupId>com.github.RoaringBitmap.RoaringBitmap</groupId> |
| // Google Mirror of Maven Central, placed first so that it's used instead of flaky Maven Central. | ||
| // See https://storage-download.googleapis.com/maven-central/index.html for more info. | ||
| "gcs-maven-central-mirror" at "https://maven-central.storage-download.googleapis.com/maven2/", | ||
| "jitpack" at "https://jitpack.io", |
There was a problem hiding this comment.
Just wondering if this can cause a flakiness like the default Maven.
Due to the Apache Spark's high traffic, the Maven was flaky. So, we are using GCS Maven as the first cache here inevitably.
There was a problem hiding this comment.
Understand your concerns. We can wait for a while longer to see if RoaringBitmap can resume its publish on Maven Central
LuciferYang
changed the title
RoaringBitmap to 1.3.19RoaringBitmap to 1.4.1
LuciferYang
changed the title
RoaringBitmap to 1.4.1RoaringBitmap to 1.5.2
2 participants
What changes were proposed in this pull request?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?