[FLINK-20787] Improve the Table API to make it usable

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 1.14.0
• Component/s: Table SQL / API
• Assignee: Unassigned
• Reporter: Dian Fu
• Created: 28/Dec/20 11:26
• Updated: 02/Apr/21 06:51

Description

Currently, there are quite a few bugs in the Table API which makes it difficult to use. Users will encounter all kinds of problems when using Table API and have to find various workarounds from time to time. This is an umbrella JIRA for all the issues specific in the Table API and trying to make the Table API smooth to use.

Issue Links

• relates to: FLINK-18605 Refactor Descriptor API (TableEnvironment#connect)

Sub-Tasks

• It doesn't support to call Table.limit() continuously: Open
• OverWindow doesn't support to order by non-time attribute in batch mode for Table API program: Open
• The time attribute is lost when constructing a Table via TableEnvironment.from: Open
• It doesn't support to join two tables containing the same field names in Table API: Open
• It doesn't support to use cube/rollup/grouping sets in the Table API: Open
• The configuration specified in TableConfig may not take effect in certain cases: Open
• Timestamp extractor created from properties does not work for some physical fields: Open
• Fix Ambiguous column name exception bug for Table API: Open
• Support to select distinct columns in the Table API: Open
• Support unnest in the Table API: Open