Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
By building Flink OLAP services internally using Flink master branch, we realized that if we want to involve more community users to use Flink OLAP, besides scheduling and execution performance improvement mentioned in FLINK-25318, we also need to improve some basic usability issues in OLAP scenarios, including providing quick start for users to build Flink OLAP service, allocating minimum resources when cluster start, displaying detailed job sql in flink ui, etc.
Meanwhile, we believe this can also optimize the user experience of running batch jobs in session cluster mode. So after talk with zjureel , we create this jira to track the progress of related work.
Attachments
Issue Links
- is a parent of
-
FLINK-25015 job name should not always be `collect` submitted by sql client
- Resolved
-
FLINK-15959 Add min number of slots configuration to limit total number of slots
- Closed
-
FLINK-32863 Improve Flink UI's time precision from second level to millisecond level
- Closed
- is related to
-
FLINK-25318 Improvement of scheduler and execution for Flink OLAP
- Open
-
FLINK-32488 Introduce configuration to control ExecutionGraph cache in REST API
- Open
- links to