Re: IgniteMultiMap design

Assigned IGNITE-642 and IGNITE-637 to me, and unassigned IGNITE-640. If nobody picks it up in the near future, I will do it (after I'm done with IGNITE-642 and IGNITE-637). Best regards, VJ On Thu, Nov 5, 2015 at 1:48 AM, Dmitriy Setrakyan wrote: > On Tue, Nov 3, 2015

Re: IgniteMultiMap design

On Wed, Nov 4, 2015 at 5:09 PM, Vladisav Jelisavcic wrote: > Assigned IGNITE-642 and IGNITE-637 to me, > and unassigned IGNITE-640. > > If nobody picks it up in the near future, > I will do it (after I'm done with IGNITE-642 and IGNITE-637). > > Best regards, > VJ > Thanks!

Re: IgniteMultiMap design

Dear Dmitriy, it sounds excellent, I would like to do it, but I would like to implement ReentrantLock first: https://issues.apache.org/jira/browse/IGNITE-642 What do you think? On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan wrote: > Igniters, > > MultiMap should be

IgniteMultiMap design

Igniters, MultiMap should be really great addition to the Ignite fabric, as it provides an easy-to-use API to work with time-series data. I have added a detailed design description to the IgniteMultiMap ticket: https://issues.apache.org/jira/browse/IGNITE-640 Vladislav Jelisavcic, the ticket is