Hello, Igor. Thanks for starting this discussion.
I think we should take a step back in it and answer the following questions: 1. What the exact issues with the H2 integration? Can you send a tickets links? Can we label all H2 integration issues in JIRA? I propose to use "h2" label. 2. What are the requirements for the new SQL engine? We should write it down and discuss. 3. What options do we have? Are there any alternatives to Calcite on the market? We did the wrong choice that looked obvious one time. So we should carefully avoid it at this time. 4. What is improvements of Ignite we want to make with the new engine? В Пт, 27/09/2019 в 08:44 +0000, Igor Seliverstov пишет: > Hi Igniters! > > As you might know currently we have many open issues relating to current H2 > based engine and its execution flow. > > Some of them are critical (like impossibility to execute particular queries), > some of them are majors (like impossibility to execute particular queries > without pre-preparation your data to have a collocation) and many minors. > > Most of the issues cannot be solved without whole engine redesign. > > So, here the proposal: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084 > > I'll appreciate if you share your thoughts on top of that. > > Regards, > Igor
signature.asc
Description: This is a digitally signed message part
