[
https://issues.apache.org/jira/browse/FLINK-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953553#comment-16953553
]
Leonard Xu edited comment on FLINK-11491 at 10/17/19 9:35 AM:
--------------------------------------------------------------
[~ykt836]
Thanks for your reminder, I rename sub-task-3 and add some explanation to make
it clear enough.
About sub-task-4 , I concern that not all queries can run successful and
stable from past experience, I plan to close it after previous 3 sub-task have
finished and all queries can run stable.
How do you think of my thought？
was (Author: leonard xu):
[~ykt836]
Thanks for your reminder, I rename sub-task-3 and and some explanation to make
it clear enough.
About sub-task-4 , I concern that not all queries can run successful and
stable from past experience, I plan to close it after previous 3 sub-task have
finished and all queries can run stable.
How do you think of my thought？
> Support all TPC-DS queries
> --------------------------
>
> Key: FLINK-11491
> URL: https://issues.apache.org/jira/browse/FLINK-11491
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Leonard Xu
> Priority: Major
> Fix For: 1.10.0
>
>
> A more detailed description can be found in
> [FLIP-32|https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions].
> This issue describes the goal of supporting all TPC-DS queries on a unified
> runtime for batch and streaming.
> Operations might not be executed with the full performance until changes in
> other Flink core components have taken place.
> This includes external catalog support and Hive integration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
