JIRA Calcite dashboards

Hello, I created two JIRA dashboards in order to track a bit better what is happening in the project. Apache Calcite Release [1] which might be helpful for release managers to have an overview of the ongoing release and take action when they deem necessary. Apache Calcite Dev Overview [2] which

Re: JIRA Calcite dashboards

Thanks Stamatis! I could imagine this being helpful. However, I'm unable to view the release dashboard. I get the messages below: Looks like we can't show you the content of this gadget due to its configuration. The filter used isn't valid or it's restricted The filter configured for this gadge

Re: JIRA Calcite dashboards

Thanks for checking Michael! I just changed the permissions for the filters involved in the JIRA. Can you check again, please? On Sun, May 26, 2019 at 11:38 PM Michael Mior wrote: > Thanks Stamatis! I could imagine this being helpful. However, I'm > unable to view the release dashboard. > > I g

Calcite slow tests and CI

Hello, I have tried various times (not only today) to run the tests tagged as slow in our suite (mvn clean install -Dcalcite.test.slow) but with no success; it always ends up with errors. I have the impression that nobody runs these tests including CI (Jenkins, Travis, AppVeyor). I went quickly

Re: JIRA Calcite dashboards

Works now. Thanks! -- Michael Mior mm...@apache.org Le dim. 26 mai 2019 à 17:50, Stamatis Zampetakis a écrit : > > Thanks for checking Michael! > > I just changed the permissions for the filters involved in the JIRA. Can > you check again, please? > > On Sun, May 26, 2019 at 11:38 PM Michael Mior

Support complete implicit type coercion (DISCUSSION)

Hi, guys. The implicit type coercion is almost supported by every production RDBMS(MYSQL[1], ORACLE[2], SQLSERVER[3]), also some Hadoop data warehouse facilitates like HIVE. As a query optimization engine of many comutation engines(like Apache Flink) and some OLAP engines(like Apache Drill), C

Re: JIRA Calcite dashboards

Hopefully the "Calcite current version Unresolved" table of the "Apache Calcite Release" dashboard can help us quickly identify ready PRs to speed up the merging process. Awesome work Stamatis, thanks! Thanks, Gelbana On Mon, May 27, 2019 at 12:21 AM Michael Mior wrote: > Works now. Thanks! >

Re: Support complete implicit type coercion (DISCUSSION)

Thanks Danny for bringing it up. This is a useful feature, we should push it forward. I went through the design doc, looks good in general. I will also spend some time on the pull request 706. Thanks ~ Haisheng Yuan -- 发件人：Yuzhao Che

Re: Support complete implicit type coercion (DISCUSSION)

Thanks Danny for pushing this. Just like you said, different engines may use different strategies for implicit type cast, so i think making the whole mechanism pluggable would be a good idea. Best, Kurt On Mon, May 27, 2019 at 11:08 AM Haisheng Yuan wrote: > Thanks Danny for bringing it up. >

Calcite-Master - Build # 1184 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #1184) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/1184/ to view the results.

calcite close connection

Hi, I am currently using calcite to access postgre and other relational databases. But throws the exception "too many clients". While I have closed the calciteConnection after performing the operation. I want to know if the connections to the underlying databases have been closed after the conne

Re: Support complete implicit type coercion (DISCUSSION)

Hi Yuzhao: Thanks for raising this discussion. I think this feature is significant to Calcite. AFAIK, there is no standard on implicit type coercion. Even for those widely-adopted RDBMSs (ORACLE, SqlSever, and etc.), we can find some "unreasonable" corner cases that are not as user expected. There

Re: Support complete implicit type coercion (DISCUSSION)

Thanks for your response, Zhu Feng, I totally agree with you. The first thing we should consider with implicit type coercion is to make it pluggable. In the original PR[1], I make implementation of different SqlNodes into separate methods, and we can inherent the TypeCoercion  interface to make