Re: Loose ends before 1.6

We’re making progress. Here’s what’s left before we can cut an RC: * https://issues.apache.org/jira/browse/CALCITE-1047 - Julian * https://issues.apache.org/jira/browse/CALCITE-1044 - Josh * https://issues.apache.org/jira/browse/CALCITE-1052 - Josh *

Re: Loose ends before 1.6

Hi Julian, I am validating Hive against the snapshot right now. It can be tracked through https://issues.apache.org/jira/browse/HIVE-12839. Thanks. Best Pengcheng On Tue, Jan 12, 2016 at 7:09 PM, Julian Hyde wrote: > We’re making progress. Here’s what’s left before we

Re: Seeming test deadlock between JdbcTest and JdbcFrontLinqBackTest

Thanks for the pointer, Vladimir. I haven't dug into this corner of the code yet, so I wasn't really sure what the guarantees on concurrency were meant to be. I plan to focus on the other issues from yesterday, but will try to swing around to this after. Anyone else who has cycles/motivation

Re: Seeming test deadlock between JdbcTest and JdbcFrontLinqBackTest

As far as I can see, the problem is "non-properly-synchronized" HashMap in ReflectiveRelMetadataProvider. The fix would probably be to using ConcurrentHashMap there, however it is better to doublecheck if there are more high-level data races there. Vladimir

Embed calcite in my application

Hello, A basic question - how do I embed calcite in my application? My application is written in C++ that connects to different datasources, runs queries, gets results and run analytics. I would like to leverage calcite to add more datasources. So I have the below questions 1. How do I embed

Re: Calcite master branch has failed unit test?

Thanks for catching up this one guys... And thanks for taking care of it Julian. I was convinced I had run the test suite on the right branch... Not the first time it happens, I will try to take more care. -- Jesús On 1/12/16, 9:07 PM, "Jinfeng Ni" wrote: >Sorry

Re: Seeming test deadlock between JdbcTest and JdbcFrontLinqBackTest

Will do. Julian Hyde wrote: I fixed a deadlock issue a few months back (CALCITE-874) but it's entirely possible I missed something, and I do see intermittent hangs in Travis-CI. Josh, can you please log a JIRA case with the stack? It's not critical for this release. On Tue, Jan 12, 2016 at

Calcite master branch has failed unit test?

On commit: git log commit 9f6f23de06791a3d2de1672b55bfdf7d6396bc78 Failed tests: SqlToRelConverterTest.testCorrelationNotExistsAndFilter:1692 plan expected:<...alFilter(condition=[[NOT(IS NOT NULL($12)])]) LogicalJoi...> but was:<...alFilter(condition=[[IS NULL($12])])

Seeming test deadlock between JdbcTest and JdbcFrontLinqBackTest

I'm seeing the occasional "deadlock" on some tests in calcite-core. The top of the stacktrace seems to get stuck in the following: "pool-1-thread-1" prio=5 tid=0x7fd50611e800 nid=0x5103 runnable [0x000115b81000] java.lang.Thread.State: RUNNABLE at