[
https://issues.apache.org/jira/browse/FLINK-22277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22277:
-----------------------------------
Labels: auto-deprioritized-minor auto-unassigned (was: auto-unassigned
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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
> Priority: Not a Priority
> Labels: auto-deprioritized-minor, auto-unassigned
>
> 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.20.1#820001)
