I believe the blog post in question is [1] and the relevant text is > Use vendor-specific protocols. For some databases, applications can use a database-specific protocol or SDK to directly get Arrow data. For example, applications could use Dremio via Arrow Flight SQL. But client applications that want to support multiple database vendors would need to integrate with each of them. (Look at all the connectors that Trino implements.) And databases like PostgreSQL don’t offer an option supporting Arrow in the first place.
I did not read that to mean FlightSQL was a vendor specific protocol, but if others did so clarifying the wording sounds like a good idea to me Perhaps you could propose a specific rephrasing on a PR to [2]. Andrew [1] https://arrow.apache.org/blog/2023/01/05/introducing-arrow-adbc/ [2] https://github.com/apache/arrow-site/blob/master/_posts/2023-01-05-introducing-arrow-adbc.md On Wed, Jan 11, 2023 at 8:02 AM James Duong <james.du...@improving.com.invalid> wrote: > Hi, > > In the ADBC blog entry that Flight SQL was mentioned as a vendor-specific > protocol and s Dremio is mentioned in the same sentence. > > The intent of the Flight SQL was to be database agnostic and this sort of > implies Flight SQL as a Dremio-specific protocol which is not really what > we want. > > Perhaps this can be rephrased? Maybe highlight that ADBC can help with > building generic Arrow-based applications that work with both databases > that have a specific Arrow-interface such as Big Query in addition to any > Flight SQL-capable sources. >
