Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Done
-
None
Description
From the mailing list:
Fabian: Flink's Table API is pretty close to what SQL provides. IMO, the best
approach would be to leverage that and build a SQL parser (maybe together
with a logical optimizer) on top of the Table API. Parser (and optimizer)
could be built using Apache Calcite which is providing exactly this.
Since the Table API is still a fairly new component and not very feature
rich, it might make sense to extend and strengthen it before putting
something major on top.
Ted: It would also be relatively simple (I think) to retarget drill to Flink if
Flink doesn't provide enough typing meta-data to do traditional SQL.
Attachments
Issue Links
- Blocked
-
FLINK-3221 Move Table API on top of Apache Calcite
- Resolved
- requires
-
FLINK-2971 Add outer joins to the Table API
- Closed
-
FLINK-2946 Add orderBy() to Table API
- Closed
-
FLINK-3152 Support all comparisons for Date type
- Resolved
-
FLINK-3139 NULL values handling in Table API
- Resolved
-
FLINK-3153 Support all comparisons for String type
- Resolved