[
https://issues.apache.org/jira/browse/FLINK-22277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22277:
-----------------------------------
Labels: stale-assigned (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed in 7 days, the
issue will be automatically unassigned.
> Refactor sql client's DynamicResult
> ------------------------------------
>
> Key: FLINK-22277
> URL: https://issues.apache.org/jira/browse/FLINK-22277
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Client
> Reporter: Kurt Young
> Assignee: Nicholas Jiang
> Priority: Minor
> Labels: stale-assigned
>
> Right now, the sql client Executor has different result handling logic for
> different result display mode.
> Different result is handled by child classes of `DynamicResult`.
> This leads to introducing page related API to the Executor, such as
> `snapshotResult` and `retrieveResultPage`, which I think is inappropriate
> and will make things complicated.
> It will be benefit to simplify the responsibility of Executor about
> retrieving results to simply streaming back the SELECT result, and move the
> logic of dealing with different display mode into CliResultView.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
