Thanks for the fantastic proposal @shuyi. I think the STRUCT idea is great
considering ROW is not standard SQL either. As a user of calcite I have a
couple questions.
Since ROW constructor is so similar with STRUCT, would it be a good idea to
consolidate the two syntax? Or have a clear
As a user of Calcite working on adding streaming SQL to Apache Beam this
sounds like a fantastic proposal. Our initial goal is to be able to run SQL
queries that transform arbitrary JSON objects. Without this syntax objects
must be flattened when they pass through the transform. Is this something
Vitalii Diravka created CALCITE-2241:
Summary: Join equality condition should be considered while
pushing down filter conditions with expressions disjunction for both tables
Key: CALCITE-2241
URL:
Zoltan Haindrich created CALCITE-2240:
-
Summary: Predicate push into CASE statment doesn't happen in some
cases
Key: CALCITE-2240
URL: https://issues.apache.org/jira/browse/CALCITE-2240
Project:
@Michael, @Albert, yes, I dont think it is SQL standard. But I think it's
very useful in the context of streaming SQL, e.g. Flink SQL, where the
sinks can be a database or endpoints with defined protobuf/thrift schema.
They usually have complex structure. Supporting complex structure in SQL
output
The Apache Jenkins build system has built Calcite-Master (build #241)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/241/ to
view the results.
