You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Shengkai Fang (Jira)" <ji...@apache.org> on 2022/12/27 01:58:00 UTC

[jira] [Assigned] (FLINK-30449) Improve Serialization and Deserialization of FetchResultsResponseBody

     [ https://issues.apache.org/jira/browse/FLINK-30449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shengkai Fang reassigned FLINK-30449:
-------------------------------------

    Assignee: yuzelin

> Improve Serialization and Deserialization of FetchResultsResponseBody
> ---------------------------------------------------------------------
>
>                 Key: FLINK-30449
>                 URL: https://issues.apache.org/jira/browse/FLINK-30449
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Gateway
>    Affects Versions: 1.17.0
>            Reporter: yuzelin
>            Assignee: yuzelin
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the REST endpoint serialize and deserialize the ResultSet in the FetchResultsResponseBody. But many information of ResultSet will be also put in the FetchResultsResponseBody, so it's not a good way. In this ticket, I propose to introduce a ResultInfo to replace the ResultSet in the FetchResultsResponseBody.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)