Hello,
>From my point of view, it's better to reduce the scope of features to
be supported and focus on those ones that a really important for
production e.g. Calcite for Ignite 2.x. However, talking in terms of
open-source development it's better to find a volunteer who will fix
all the issues yo
Nikita,
Thank you for starting this thread.
+1 for these dates, but I think it's better to start the code freeze
date when the Calcite engine will be actually merged to the master
branch.
On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev wrote:
>
> Dear Ignite Community!
>
> I suggest starting Apache
Created the issue [1] to solve the problem of broken checks we already have
because of non-guaranted checks by Travis.
https://issues.apache.org/jira/browse/IGNITE-16508
As for me, I believe that this should be removed. We have already proven
binary protocol that is under heavy use.
ср, 9 февр. 2022 г. в 15:11, Maxim Muzafarov :
> Hello,
>
> From my point of view, it's better to reduce the scope of features to
> be supported and focus on those ones that a really
