+1

08.12.2020, 23:47, "Andrey Mashenkov" <andrey.mashen...@gmail.com>:
> +1
>
> On Tue, Dec 8, 2020 at 11:22 PM Igor Seliverstov <gvvinbl...@gmail.com>
> wrote:
>
>>  +1
>>
>>  08.12.2020 22:38, Andrey Gura пишет:
>>  > +1
>>  >
>>  > On Tue, Dec 8, 2020 at 10:02 PM Nikolay Izhikov <nizhi...@apache.org>
>>  wrote:
>>  >> +1
>>  >>
>>  >>> 8 дек. 2020 г., в 21:54, Valentin Kulichenko <
>>  valentin.kuliche...@gmail.com> написал(а):
>>  >>>
>>  >>> +1
>>  >>>
>>  >>> On Tue, Dec 8, 2020 at 8:31 AM Вячеслав Коптилин <
>>  slava.kopti...@gmail.com>
>>  >>> wrote:
>>  >>>
>>  >>>> Hello Igniters,
>>  >>>>
>>  >>>> I want to start voting on removing the public API (and eventually all
>>  >>>> unused parts) related to the MVCC feature.
>>  >>>>
>>  >>>> This topic has already been discussed many times (at least, [1], [2])
>>  and
>>  >>>> the community has agreed the feature implementation must be
>>  reapproached,
>>  >>>> because using coordinator node for transactions ordering and 2pc
>>  protocol
>>  >>>> is slow by design and will not scale well. [3]
>>  >>>>
>>  >>>> Moreover, the current implementation has critical issues [4], not
>>  supported
>>  >>>> by the community, and not well tested at all.
>>  >>>>
>>  >>>> Removing the public API first will allow us to clean up the code
>>  later step
>>  >>>> by step without rushing and keep intact useful improvements that are
>>  >>>> already in use or can be reused for other parts in the future.
>>  >>>> For instance, partition counters implementation is already adapted to
>>  fix
>>  >>>> tx caches protocol issues [5].
>>  >>>>
>>  >>>> The future of MVCC is unclear for now, but, definitely, this feature
>>  is
>>  >>>> useful for a lot of user scenarios and can be scheduled for later
>>  Ignite
>>  >>>> versions.
>>  >>>> Also, the MVCC feature is in an experimental state, so it can be
>>  modified
>>  >>>> in any way, I think.
>>  >>>>
>>  >>>> +1 - to accept removing MVVC feature from public API
>>  >>>> 0 - don't care either way
>>  >>>> -1 - do not accept removing API (explain why)
>>  >>>>
>>  >>>> The vote will hold for 7 days and will end on Wednesday, December
>>  16th at
>>  >>>> 19:00 UTC:
>>  >>>>
>>  >>>>
>>  
>> https://www.timeanddate.com/countdown/generic?iso=20201216T19&p0=1440&font=cursive
>>  >>>>
>>  >>>> [1]
>>  >>>>
>>  >>>>
>>  
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
>>  >>>> [2]
>>  >>>>
>>  >>>>
>>  
>> http://apache-ignite-developers.2346864.n4.nabble.com/Disable-MVCC-test-suites-td50416.html
>>  >>>> [3]
>>  >>>>
>>  >>>>
>>  
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-tp45669p45727.html
>>  >>>> [4]
>>  >>>>
>>  >>>>
>>  
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-tp45669p45716.html
>>  >>>> [5]
>>  >>>>
>>  >>>>
>>  
>> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-tp45669p45714.html
>>  >>>>
>>  >>>> Thanks,
>>  >>>> Slava.
>>  >>>>
>
> --
> Best regards,
> Andrey V. Mashenkov

Reply via email to