Hello! I have recently started to look into integrating Flight RPC with Acero source/sink node.
In Flight, the life cycle of a "read" request looks sth like: - User specifies a URL (e.g. my_storage://my_path) and parameter (e.g., begin = "20220101", end = "20220201") - Client issue GetFlightInfo and get FlightInfo from server - Client issue DoGet with the FlightInfo and get a stream reader - Client calls Nextuntil stream is exhausted My question is, how does the above life cycle fit in an Acero node? In other words, what are the proper places in Acero node lifecycle to issue the corresponding flight RPC? Appreciate any thoughts, Li
