[jira] [Created] (CALCITE-3129) Automate website builds

Francis Chuang created CALCITE-3129: --- Summary: Automate website builds Key: CALCITE-3129 URL: https://issues.apache.org/jira/browse/CALCITE-3129 Project: Calcite Issue Type: Task

Re: [DISCUSS] Towards Calcite 1.20.0

Thanks for being RM for this massive release, Michael! I was hoping to get website built automation included in this release, but I ran into a few blocking issues with Jenkins and it will probably have to be done after 1.19. Francis On 15/06/2019 9:02 am, Julian Hyde wrote: Hey everyone.

Re: [DISCUSS] Towards Calcite 1.20.0

Hey everyone. I’m on vacation (camping in the mountains) next week, so I’ll miss the vote. Still, I’m very much hoping that the vote moves forward, and we have a release by the end of next week. With 171 commits since 1.19, this will be our second largest release ever (second only to 1.17,

Re: calcite connection and thread safety

> Only one thread should access a connection (or objects created from that connection, such as statements and result sets) at a time. Does it mean that two statements created by same connection can't be processed in parallel by different threads ? For example if one synchronizes just on statement

Re: Null collation error when connecting to Hive DB

Thank you for the quick response, Julian. I'll implement your advice. -Val On Fri, Jun 14, 2019 at 11:34 AM Julian Hyde wrote: > It looks as if there is a Hive bug logged for this issue: > https://issues.apache.org/jira/browse/HIVE-4806 < > https://issues.apache.org/jira/browse/HIVE-4806> and

Re: Null collation error when connecting to Hive DB

It looks as if there is a Hive bug logged for this issue: https://issues.apache.org/jira/browse/HIVE-4806 and it has a patch that has not been accepted. But there could be a much simpler patch - nullsAreSortedLow should return true, and the

Null collation error when connecting to Hive DB

Hi All, I'm using Calcite to connect to Hive DB via JDBC adapter that connects to Thrift JDBC server running on a VM with Spark and Hive installed there. The schema looks like this: { name: 'thrift', type: 'custom', factory: 'org.apache.calcite.adapter.jdbc.JdbcSchema$Factory', operand:

Re: calcite connection and thread safety

The general JDBC specification is that connections are not thread-safe. Only one thread should access a connection (or objects created from that connection, such as statements and result sets) at a time. The exception is the Statement.cancel() method, which can safely be called from another

calcite connection and thread safety

Hello, I couldn't find any recommendations on using calcite connection (JdbcSchema) in a multi-threaded environment. Probably throwing DataSource on the top of calcite connection is a wrong thing to do since it doesn't create connections by itself rather delegates to existing pools. After

Re: Joining two tables while each table returns a single row of nulls

It probably doesn’t matter very much. Every join algorithm has to be able to generate a Cartesian product. E.g. if you have 2 records in the EMP table with DEPTNO=10 and 3 records in the DEPT table with DEPTNO=10 then the join needs to generate 6 rows. I see a cross-join (i.e. JOIN … ON TRUE)

[jira] [Created] (CALCITE-3128) Joining two tables producing only NULLs will return 0 rows

Muhammad Gelbana created CALCITE-3128: - Summary: Joining two tables producing only NULLs will return 0 rows Key: CALCITE-3128 URL: https://issues.apache.org/jira/browse/CALCITE-3128 Project:

Re: [DISCUSS] Towards Calcite 1.20.0

Thanks all for the suggestions. Release notes updated. -- Michael Mior mm...@apache.org Le ven. 14 juin 2019 à 01:05, Julian Hyde a écrit : > > I think you should expand the "breaking changes" section of the > release notes and note that classes SemiJoin, EnumerableSemiJoin, > SemiJoinType and

Re: Joining two tables while each table returns a single row of nulls

It's a bug. Please log it. I got the following plan, which looks correct. > explain plan for select * from (select nullif(5,5)), (select nullif(5,5)); EnumerableHashJoin(condition=[true], joinType=[inner]) EnumerableCalc(expr#0=[{inputs}], expr#1=[null:INTEGER], EXPR$0=[$t1])