This is great news!
Alex, thanks for making it to the end!
--
Regards,
Konstantin Orlov
> On 24 Mar 2022, at 18:07, Alex Plehanov wrote:
>
> Hello Igniters,
>
> I've merged the pull request. The Calcite-based SQL engine is in the master
> branch now.
> If you desire to try it, you can fin
Great job!
On Thu, Mar 24, 2022 at 6:27 PM Nikita Amelchev
wrote:
> Great news!
>
> I will cut the 2.13 release branch soon.
>
> чт, 24 мар. 2022 г. в 18:07, Alex Plehanov :
>
> >
> > Hello Igniters,
> >
> > I've merged the pull request. The Calcite-based SQL engine is in the
> master
> > branch
Great news!
I will cut the 2.13 release branch soon.
чт, 24 мар. 2022 г. в 18:07, Alex Plehanov :
>
> Hello Igniters,
>
> I've merged the pull request. The Calcite-based SQL engine is in the master
> branch now.
> If you desire to try it, you can find configuration instructions in
> modules/calc
Hello Igniters,
I've merged the pull request. The Calcite-based SQL engine is in the master
branch now.
If you desire to try it, you can find configuration instructions in
modules/calcite/README.txt file.
вс, 6 мар. 2022 г. в 13:03, Alex Plehanov :
> Hello Igniters,
>
> I've prepared the pull re
Hello Igniters,
I've prepared the pull request [1] and have plans to merge it to the master
branch in about two weeks, if there is no objection.
[1]: https://github.com/apache/ignite/pull/9855
чт, 30 дек. 2021 г. в 13:43, Anton Vinogradov :
> > it would be great to release a new SQL engine in 2
> it would be great to release a new SQL engine in 2.13 as an
experimental feature.
++1
On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov
wrote:
> Andrey,
>
> > Is this [1] a full scope of the tickets that MUST be resolved before the
> engine could be merged?
> Yes, we must resolve at least these
Andrey,
> Is this [1] a full scope of the tickets that MUST be resolved before the
engine could be merged?
Yes, we must resolve at least these tickets before merging. If you see any
other release blockers fill free to attach them to this ticket.
> I think we have to add instructions to the readm
Alex,
it would be great to release a new SQL engine in 2.13 as an
experimental feature.
Is this [1] a full scope of the tickets that MUST be resolved before the
engine could be merged?
I think we have to add instructions to the readme file on how to turn a new
SQL engine on.
Also, I don't like th
Alex, great !
If someone wants to touch codebase somehow plz use this branch [1]
Test passed can be found here [2] [3]
[1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite
[2]
https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/in
I forgot to attach links:
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
[2]: https://github.com/apache/ignite/tree/sql-calcite
ср, 29 дек. 2021 г. в 21:00, Alex Plehanov :
> Hello, Igniters!
>
> As you may already know there is the new Ignite SQL e
Hello, Igniters!
As you may already know there is the new Ignite SQL engine based on Apache
Calcite currently under development.
Reasons to move from H2-based engine and motivation for creating the new
one in details described in IEP-37 [1].
You can find all related to the new engine source code
11 matches
Mail list logo
