You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/24 10:44:00 UTC

[jira] [Updated] (FLINK-22277) Refactor sql client's DynamicResult

     [ 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-unassigned stale-minor  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-unassigned, stale-minor
>
> 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)