-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Update bytebuffer-collections to 0.2.5 #3117
Conversation
drcrallen
commented
Jun 8, 2016
- Adds polygound bound for spatial data. Thanks @scusjs
- Fixes cache key collisions for spatial data
- Update roaring to 0.5.18
lol, those labels were not at all what I had put on there originally. Github, you are silly |
@drcrallen I had a similar thing happen to me earlier today and thought I was just losing my mind |
👍 |
BTW: Why not a newer roaring? Looks like there are newer 0.5.x's, and also 0.6.x's are a thing. https://github.com/RoaringBitmap/RoaringBitmap/blob/master/CHANGELOG |
@gianm because noone submitted a thing to bytebuffer-collections |
I don't know what the compatibility between 0.5.x and 0.6.x is. Maybe @lemire can comment if there would be any unexpected things happen to things created with 0.5.x roaring if we updated to 0.6.x? |
The API and the file format should be considered stable. We are mostly just optimizing performance, reducing memory usage and adding (small) features. Upgrading to the latest version should not be an issue and you should expect performance and memory-usage gains. If any issue should arise (unlikely), we are there to help. It is recommended to update to version 0.6 of RoaringBitmap except if you need Java 6 support. We deliberately stopped testing Java 6 with version 0.6. But if anyone is using Druid with Java 6, they have other problems, presumably... |
Yes, like "rejected jars" kind of problems. Thanks! |
|
👍 |