Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
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 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 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.13 as an > > >> experimental feature. > > >> ++1 > > >> > > >> On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov < > plehanov.a...@gmail.com> > > >> 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 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 readme file on how to > turn > > >> a > > >> > new SQL engine on. > > >> > Sure, I think it should be the part of documentation ticket. > > >> > > > >> > > Also, I don't like the module name "ignite-calcite", because > Calcite > > >> is > > >> > an independent project. > > >> > Personally, I see no problems here (but it's discussable). We have a > > >> lot of > > >> > modules where the name is an independent project: "ignite-kafka", > > >> > "ignite-spring", "ignite-kubernetes", "ignite-log4j", > > >> "ignite-zookeeper", > > >> > etc. > > >> > > > >> > > So, would you mind renaming the module to e.g. > "ignite-sql-engine" or > > >> > "ignite-sql"? > > >> > Module "ignite-indexing" also contains SQL engine, so names like > > >> > "ignite-sql-engine" or "ignite-sql" will be ambiguous. > > >> > > > >> > чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov < > > >> andrey.mashen...@gmail.com > > >> > >: > > >> > > > >> > > 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 the module name "ignite-calcite", because > Calcite > > >> is > > >> > an > > >> > > independent project. > > >> > > and Ignite just uses it. > > >> > > So, would you mind renaming the module to e.g. > "ignite-sql-engine" or > > >> > > "ignite-sql"? > > >> > > > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > > >> > > > > >> > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky > > >> > > wrote: > > >> > > > > >> > > > > > >> > > > 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/internal/processors/query/calcite > > >> > > > [3] > > >> > > > > > >> > > > > >> > > > >> > https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > > >> > > > > > >> > > > > > > >> > > > >> > > >> > > > >>>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 > changes in > > >> > the > > >> > > > >>>"sql-calcite" branch [2]. > > >> > > > >>> > > >> > > > >>>Calcite-based SQL engine is not production-ready yet and has > a > > >> lot > > >> > of > > >> > > > known > > >> > > > >>>issues. In the future, the new engine should be fully > > >> independent of > > >> > > > >>>"ignite-indexing" and H2, but now it relies on schema > management > > >> and > > >> > > > >>>indexes implemented in the "ignite-indexing" module and can't > > >> work > > >> > > > without > > >> > > > >>>the old engine. Despite all of the above mentioned, in the > > >> current > > >> > > > state, > > >> > > > >>>it has its own parsing, planning and execution flow and is > > >> almost as > > >> > >
Empty test report for 'Control-utility' and 'Zookeeper
Hi everyone, As I see, both 'Control Utility' and 'Control Utility (Zookeeper)' test suites have empty test results and there are messages in a build log as below: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Above problem occurs both on TC1 and TC2 [1-4] for the master branch, but does not on the 'ignite-2.12' [5-8]. Can anyone take a look, please? Links: 1. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6480112?showLog=6480112_1061_895 2. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6480111?showLog=6480111_1060_894 3. https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6359892?showRootCauses=true=6359892_1003_909 4. https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6359893?showRootCauses=true=6359893_1003_909 . 5. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6479329 6. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6479328 7. https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6359189?showRootCauses=true=true 8. https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6359190?showRootCauses=true=true
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
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/calcite/README.txt file. > > вс, 6 мар. 2022 г. в 13:03, Alex Plehanov : > > > 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.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 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 readme file on how to turn > >> a > >> > new SQL engine on. > >> > Sure, I think it should be the part of documentation ticket. > >> > > >> > > Also, I don't like the module name "ignite-calcite", because Calcite > >> is > >> > an independent project. > >> > Personally, I see no problems here (but it's discussable). We have a > >> lot of > >> > modules where the name is an independent project: "ignite-kafka", > >> > "ignite-spring", "ignite-kubernetes", "ignite-log4j", > >> "ignite-zookeeper", > >> > etc. > >> > > >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or > >> > "ignite-sql"? > >> > Module "ignite-indexing" also contains SQL engine, so names like > >> > "ignite-sql-engine" or "ignite-sql" will be ambiguous. > >> > > >> > чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov < > >> andrey.mashen...@gmail.com > >> > >: > >> > > >> > > 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 the module name "ignite-calcite", because Calcite > >> is > >> > an > >> > > independent project. > >> > > and Ignite just uses it. > >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or > >> > > "ignite-sql"? > >> > > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > >> > > > >> > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky > >> > > wrote: > >> > > > >> > > > > >> > > > 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/internal/processors/query/calcite > >> > > > [3] > >> > > > > >> > > > >> > > >> https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql > >> > > > > >> > > > > > >> > > > >> > >> > > > >>>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 changes in > >> > the > >> > > > >>>"sql-calcite" branch [2]. > >> > > > >>> > >> > > > >>>Calcite-based SQL engine is not production-ready yet and has a > >> lot > >> > of > >> > > > known > >> > > > >>>issues. In the future, the new engine should be fully > >> independent of > >> > > > >>>"ignite-indexing" and H2, but now it relies on schema management > >> and > >> > > > >>>indexes implemented in the "ignite-indexing" module and can't > >> work > >> > > > without > >> > > > >>>the old engine. Despite all of the above mentioned, in the > >> current > >> > > > state, > >> > > > >>>it has its own parsing, planning and execution flow and is > >> almost as > >> > > > >>>functional as the H2-based SQL engine. > >> > > > >>> > >> > > > >>>Some users are already interested in the Calcite-based engine and > >> > > asking > >> > > > >>>about the development status and release dates. Calcite-based SQL > >> > > engine > >> > > > >>>will be the only SQL engine in Ignite 3.0. Perhaps even in 2.x we > >> > can > >> > > > get > >> > > > >>>rid of the H2-based engine at some time in
Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature
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 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.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 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 readme file on how to turn >> a >> > new SQL engine on. >> > Sure, I think it should be the part of documentation ticket. >> > >> > > Also, I don't like the module name "ignite-calcite", because Calcite >> is >> > an independent project. >> > Personally, I see no problems here (but it's discussable). We have a >> lot of >> > modules where the name is an independent project: "ignite-kafka", >> > "ignite-spring", "ignite-kubernetes", "ignite-log4j", >> "ignite-zookeeper", >> > etc. >> > >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or >> > "ignite-sql"? >> > Module "ignite-indexing" also contains SQL engine, so names like >> > "ignite-sql-engine" or "ignite-sql" will be ambiguous. >> > >> > чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov < >> andrey.mashen...@gmail.com >> > >: >> > >> > > 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 the module name "ignite-calcite", because Calcite >> is >> > an >> > > independent project. >> > > and Ignite just uses it. >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or >> > > "ignite-sql"? >> > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 >> > > >> > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky >> > > wrote: >> > > >> > > > >> > > > 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/internal/processors/query/calcite >> > > > [3] >> > > > >> > > >> > >> https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql >> > > > >> > > > > >> > > > >> >> > > > >>>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 changes in >> > the >> > > > >>>"sql-calcite" branch [2]. >> > > > >>> >> > > > >>>Calcite-based SQL engine is not production-ready yet and has a >> lot >> > of >> > > > known >> > > > >>>issues. In the future, the new engine should be fully >> independent of >> > > > >>>"ignite-indexing" and H2, but now it relies on schema management >> and >> > > > >>>indexes implemented in the "ignite-indexing" module and can't >> work >> > > > without >> > > > >>>the old engine. Despite all of the above mentioned, in the >> current >> > > > state, >> > > > >>>it has its own parsing, planning and execution flow and is >> almost as >> > > > >>>functional as the H2-based SQL engine. >> > > > >>> >> > > > >>>Some users are already interested in the Calcite-based engine and >> > > asking >> > > > >>>about the development status and release dates. Calcite-based SQL >> > > engine >> > > > >>>will be the only SQL engine in Ignite 3.0. Perhaps even in 2.x we >> > can >> > > > get >> > > > >>>rid of the H2-based engine at some time in the future. There is >> some >> > > > syntax >> > > > >>>difference between Calcite and H2 (Calcite is closer to SQL >> > standards >> > > > than >> > > > >>>H2) and a totally new execution flow. After the release of this >> > > feature, >> > > > >>>users can try their queries and determine if any adaptation for >> them >> > > is >> > > > >>>required. With the new planning and execution
[GitHub] [ignite-nodejs-thin-client] NSAmelchev merged pull request #5: IGNITE-16651: replace logger with ignite-log4j2
NSAmelchev merged pull request #5: URL: https://github.com/apache/ignite-nodejs-thin-client/pull/5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ignite.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
