t; > lock, unlock events. Another one is introducing special lock event
> > for
> > > > > MVCC, but it will be confusing. Also, I see an option of firing
> only
> > > > > EVT_CACHE_OBJECT_LOCKED.
> > > > >
> > > > > Last, is differen
the same
> > key
> > > > and different modes. For ATOMIC 2 put and 1 remove event will be
> fired.
> > > For
> > > > TRANSACTIONAL 1 put will be fired in case of commit and nothing in
> case
> > > of
> > > > rollback. For MVCC
AL 1 put will be fired in case of commit and nothing in case
> > of
> > > rollback. For MVCC in current vision 2 put will be fired regardless
> > whether
> > > transaction was committed and rolled back. Currently I do not see
> options
> > > how to overco
;
> > Also, I hardly imagine current use cases for cache events. I think that
> > understanding them is the best way for developing working solution for
> > MVCC.
> >
> > I need your opinions.
> >
> > 2018-09-21 12:54 GMT+03:00 Павлухин Иван :
> >
> > &g
eveloping working solution for
> MVCC.
>
> I need your opinions.
>
> 2018-09-21 12:54 GMT+03:00 Павлухин Иван :
>
> > Hi Igniters,
> >
> > As you might know MVCC was introduced in Apache Ignite. We started
> > IgniteEvents implementation for MVCC caches and fa
MT+03:00 Павлухин Иван :
>
> > Hi Igniters,
> >
> > As you might know MVCC was introduced in Apache Ignite. We started
> > IgniteEvents implementation for MVCC caches and faced some obstacles. I
> > would like to start a discussion about next steps which should
you might know MVCC was introduced in Apache Ignite. We started
> IgniteEvents implementation for MVCC caches and faced some obstacles. I
> would like to start a discussion about next steps which should be done to
> deal with current problems.
>
> --
> Best regards,
> Ivan Pavlukhin
>
--
Best regards,
Ivan Pavlukhin
Hi Igniters,
As you might know MVCC was introduced in Apache Ignite. We started
IgniteEvents implementation for MVCC caches and faced some obstacles. I
would like to start a discussion about next steps which should be done to
deal with current problems.
--
Best regards,
Ivan Pavlukhin
