Hello, I'd like to propose a slight update to Flight RPC to make Flight SQL work better in different deployment scenarios. Comments on the doc would be appreciated:
https://docs.google.com/document/d/1g9M9FmsZhkewlT1mLibuceQO8ugI0-fqumVAXKFjVGg/edit?usp=sharing The gist is that FlightEndpoint allows specifying either (1) a list of concrete URIs to fetch data from or (2) no URIs, meaning to fetch from the Flight RPC service itself; but it would be useful to combine both behaviors (try these concrete URIs and fall back to the Flight RPC service itself) without requiring the service to know its own public address. Best, David
