[
https://issues.apache.org/jira/browse/ARROW-17052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17596894#comment-17596894
]
quanghgx commented on ARROW-17052:
----------------------------------
Hi [~lidavidm]
I have a couple of queries that need your help.
1. Please help me on the list of structures that need to expose
serialize/deserialize methods? From scanning of cpp/arrow/flight/types.h and
Flight.proto, I got:
Todo list:
# Action (done, [as the first
step|https://github.com/apache/arrow/pull/13986])
# ActionType
# Criteria
# Result
# FlightEndpoint
# FlightPayload (corresponds to FlightData)
Already have serialize/deserialize
{noformat}
BasicAuth
FlightDescriptor
Ticket
FlightInfo{noformat}
No need to add?
{noformat}
Empty
PutResult
Location (has Parse and a number of methods like ForGrpcTcp)
SchemaResult (has GetSchema and serialized_schema){noformat}
2. And parts, like language bindings or existing use cases, for example, that
are related to this change? I checked arrow-flight.*-test, however, I worry if
I am missing something.
Sincerely,
> [C++][Python][FlightRPC] Ensure ::Serialize and ::Deserialize are
> consistently implemented
> ------------------------------------------------------------------------------------------
>
> Key: ARROW-17052
> URL: https://issues.apache.org/jira/browse/ARROW-17052
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, FlightRPC, Python
> Reporter: David Li
> Priority: Major
> Labels: good-first-issue, good-second-issue,
> pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Structures like Action don't expose these methods even though ones like
> FlightInfo do.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
