Danny Chan created CALCITE-3201:
---
Summary: Skip validation for sql insert columns with column
strategy that can not insert into
Key: CALCITE-3201
URL: https://issues.apache.org/jira/browse/CALCITE-3201
The Apache Jenkins build system has built Calcite-Master (build #1261)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/1261/ to
view the results.
The Apache Jenkins build system has built Calcite-Master (build #1260)
Status: Failure
Check console output at https://builds.apache.org/job/Calcite-Master/1260/ to
view the results.
I don’t think we ever considered that case.
Can you please log it, so that it is on record.
I haven’t analyzed the issue, but my instinct is that it is a reasonable
behavior to want and expect, and that it is not that difficult to fix, and if
so, someone should fix it.
Julian
> On Jul 17,
I think I saw a message asking the same thing but I'm unable to dig it up
as I can't quite remember the subject. Is there a test class that executes
SQL queries and access the results without using the JDBC API ?
Here is my attempt:
---
Planner planner =
Julian>It is difficult to build LICENSE and NOTICE files automatically
So what?
I claim that automatic license compilation produces better results than
currently present license files in Apache Calcite source code.
I claim that automatic license compilation produces better results than
currently
Dear all,
For some time now I have been getting issues with getiing materialized view
union rewriting to work using the HepPlanner.
A few weeks ago I have been able to find the culprit and I was wondering
whether this is supposed to be intended behaviour.
in [1] the code suggests that you go
