I’d be interested to hear what changes, if any, are needed to Arrow to make it 
possible to use alongside RoaringBitmap. It’s quite possible that Arrow is fine 
as it is.

Arrow goes a little beyond a pure format, because it includes memory management 
and RPC. I wonder how those affect RoaringBitmap data.

Julian


> On Dec 19, 2016, at 11:34 AM, Gary <ga...@apache.org> wrote:
> 
> Hi Julian,
> 
> It is great to know the RoaringBitmap from you, We'd like to have this 
> combination of Arrow and RoaringBitmap that will also be very valuable for 
> Apache Mnemonic (incubating) to work with Apache Arrow, Thanks.
> 
> Very truly yours.
> +Gary.
> 
> 
> On 12/19/2016 9:19 AM, Julian Hyde wrote:
>> Now that this specification is published, RoaringBitmap is now on a par with 
>> Arrow: it has C and Java implementations, and a language-independent format 
>> specification. And, I think, complementary to Arrow.
>> 
>> Does anyone have an application that needs a combination of Arrow and 
>> RoaringBitmap data?
>> 
>> Julian
>> 
>> 
>>> Begin forwarded message:
>>> 
>>> From: Daniel Lemire <lem...@gmail.com>
>>> Subject: [druid-dev] Roaring format specification published
>>> Date: December 19, 2016 at 8:32:25 AM PST
>>> To: Druid Development <druid-developm...@googlegroups.com>
>>> Reply-To: druid-developm...@googlegroups.com
>>> 
>>> We have published a Java-independent format specification, see 
>>> https://github.com/RoaringBitmap/RoaringFormatSpec
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Druid Development" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to druid-development+unsubscr...@googlegroups.com 
>>> <mailto:druid-development+unsubscr...@googlegroups.com> 
>>> <mailto:druid-development+unsubscr...@googlegroups.com 
>>> <mailto:druid-development+unsubscr...@googlegroups.com>>.
>>> To post to this group, send email to druid-developm...@googlegroups.com 
>>> <mailto:druid-developm...@googlegroups.com><mailto:druid-developm...@googlegroups.com
>>>  <mailto:druid-developm...@googlegroups.com>>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/druid-development/27b163d9-98ad-4780-b647-f11fc50b3eef%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/druid-development/27b163d9-98ad-4780-b647-f11fc50b3eef%40googlegroups.com><https://groups.google.com/d/msgid/druid-development/27b163d9-98ad-4780-b647-f11fc50b3eef%40googlegroups.com?utm_medium=email&utm_source=footer
>>>  
>>> <https://groups.google.com/d/msgid/druid-development/27b163d9-98ad-4780-b647-f11fc50b3eef%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout><https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>>.

Reply via email to