Hi David, Yes, it is. I can handle it with app_metadata field, but it would be better to have a standard means.
Thank you. -----Original Message----- From: "David Li" <lidav...@apache.org> To: <dev@arrow.apache.org>; Cc: Sent: 2024-02-16 (금) 05:13:23 (UTC+09:00) Subject: Re: Flight RPC: Add total_records and total_bytes to FlightEndpoint Hi Taeyun, Is this related to the previous thread about fetching a part of a result set? I think it's reasonable to have these fields. If others agree the next step would be to create a PR with an implementation for review/voting. Best, David On Wed, Feb 14, 2024, at 18:58, 김태연 (Taeyun Kim) wrote: > Hi, > > Currently, FlightInfo has total_records and total_bytes fields, but > FlightEndpoint does not. > It would be great if FlightEndpoint also had these fields. > These fields can be used for: > - identifying the endpoint containing a specific record by offset among > multiple endpoints. > - efficiently distributing the processing load of endpoints based on > their record count or size. > Since FlightInfo already has these fields, it might not be technically > difficult to add them to individual FlightEndpoints. > > If creating an issue in GitHub is more appropriate, I will do so. > > Thank you.
