Re: Apache Zeppelin with Calcite JDBC adapters

Thanks! That makes sense. Avatica supports the commit() call, but not Calcite :) Sitting in a coffee shop killing time. Let me see if I can knock out CALCITE-2065 ;) On 11/22/17 11:52 AM, Christian Tzolov wrote: Hi Josh, Here ​is ​Z eppelin ​'s JDBC Interpreter forcefull auto-commit

Re: Apache Zeppelin with Calcite JDBC adapters

Hi Julian, Indeed i believe that ability to set the autoCommit through the jdbc URL should solve this. Here is the ticket: https://issues.apache.org/jira/browse/CALCITE-2065 On 23 November 2017 at 00:37, Julian Hyde wrote: > Can you log that a JIRA case to make “autoCommit”

Re: Apache Zeppelin with Calcite JDBC adapters

Can you log that a JIRA case to make “autoCommit” an accepted parameter in the JDBC URL? I think it would solve this problem. > On Nov 22, 2017, at 8:52 AM, Christian Tzolov wrote: > > Hi Josh, > > Here > ​is > ​Z > eppelin > ​'s JDBC Interpreter forcefull auto-commit

Re: Apache Zeppelin with Calcite JDBC adapters

Hi Josh, Here ​is ​Z eppelin ​'s JDBC Interpreter forcefull auto-commit implementation​ : http://bit.ly/2zrykP9 ​So if the connection is not auto-commit = true the JDBC interpreter will forcefully call commit. But Avatica's connection defaults to auto-commit = true and there is no way to

Re: Apache Zeppelin with Calcite JDBC adapters

Hey Christian, Thanks for sharing this. Sounds cool. I'm curious what you mean when you say that the Avatica connection doesn't support commit. This was implemented in CALCITE-767. Also, is there a reason that Zeppelin needs a property to control autoCommit and can't use the