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.
