That sounds reasonable to me. We should add this to the docs for the JDBC driver. (Just to double check, these parameters are sent on every call?)
Does it make sense to also document the connection URI format more generally? The ADBC driver does not yet do this. If you want to put that on the PR [1] I can get to it at some point. -David [1]: https://github.com/apache/arrow/pull/14082 On Fri, Oct 21, 2022, at 06:42, James Duong wrote: > In the JDBC driver for Flight SQL, the driver will transmit unrecognized > options on the connection URI as CallHeaders: > https://github.com/apache/arrow/blob/2f627c213fc328ca7cd058d4455581fc246837da/java/flight/flight-sql-jdbc-driver/src/main/java/org/apache/arrow/driver/jdbc/utils/ArrowFlightConnectionConfigImpl.java#L152 > > The ODBC driver has the same behavior. > > It would be good if this were documented formally as a standard way > of sending and receiving data source-specific connection information in > FlightSQL sources. The PR for easily sending/receiving headers was > written with this purpose in mind (https://github.com/apache/arrow/pull/8572 > ) > > Does the ADBC driver for Flight SQL also do this? > > -- > > *James Duong* > Lead Software Developer > Bit Quill Technologies Inc. > Direct: +1.604.562.6082 | jam...@bitquilltech.com > https://www.bitquilltech.com > > This email message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. Any unauthorized review, > use, disclosure, or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy > all copies of the original message. Thank you.
