IgniteMultiMap design

[dsetrakyan]

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 currently assigned to you. If you still
intend to work on it,  please review it and let us know if the design makes
sense.

Also, would be nice if others could review it and provide comments as well.

D.

[Vladisav Jelisavcic]

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 <[hidden email]>
wrote:

> 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 currently assigned to you. If you still
> intend to work on it,  please review it and let us know if the design makes
> sense.
>
> Also, would be nice if others could review it and provide comments as well.
>
> D.
>

[dsetrakyan]

On Tue, Nov 3, 2015 at 5:46 AM, Vladisav Jelisavcic <[hidden email]>
wrote:

> 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?
>

Vladisav, this sounds great! Both, ReentrantLock and ReentrantReadWriteLock
are pretty important data structures that Ignite should support.

Can you please assign the IGNITE-642 to yourself and unassign the
IGNITE-640 to see if someone else in the community will be interested in
picking it up in the mean time?

>
>
> On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > 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 currently assigned to you. If you
> still
> > intend to work on it,  please review it and let us know if the design
> makes
> > sense.
> >
> > Also, would be nice if others could review it and provide comments as
> well.
> >
> > D.
> >
>

[Vladisav Jelisavcic]

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 <[hidden email]>
wrote:

> On Tue, Nov 3, 2015 at 5:46 AM, Vladisav Jelisavcic <[hidden email]>
> wrote:
>
> > 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?
> >
>
> Vladisav, this sounds great! Both, ReentrantLock and ReentrantReadWriteLock
> are pretty important data structures that Ignite should support.
>
> Can you please assign the IGNITE-642 to yourself and unassign the
> IGNITE-640 to see if someone else in the community will be interested in
> picking it up in the mean time?
>
>
> >
> >
> > On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan <[hidden email]
> >
> > wrote:
> >
> > > 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 currently assigned to you. If you
> > still
> > > intend to work on it,  please review it and let us know if the design
> > makes
> > > sense.
> > >
> > > Also, would be nice if others could review it and provide comments as
> > well.
> > >
> > > D.
> > >
> >
>

[dsetrakyan]

On Wed, Nov 4, 2015 at 5:09 PM, Vladisav Jelisavcic <[hidden email]>
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! If you continue at this rate, we will have no choice but to make
you a committer :)

>
> On Thu, Nov 5, 2015 at 1:48 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > On Tue, Nov 3, 2015 at 5:46 AM, Vladisav Jelisavcic <[hidden email]
> >
> > wrote:
> >
> > > 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?
> > >
> >
> > Vladisav, this sounds great! Both, ReentrantLock and
> ReentrantReadWriteLock
> > are pretty important data structures that Ignite should support.
> >
> > Can you please assign the IGNITE-642 to yourself and unassign the
> > IGNITE-640 to see if someone else in the community will be interested in
> > picking it up in the mean time?
> >
> >
> > >
> > >
> > > On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan <
> [hidden email]
> > >
> > > wrote:
> > >
> > > > 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 currently assigned to you. If you
> > > still
> > > > intend to work on it,  please review it and let us know if the design
> > > makes
> > > > sense.
> > > >
> > > > Also, would be nice if others could review it and provide comments as
> > > well.
> > > >
> > > > D.
> > > >
> > >
> >
>