Hi Gavin, This is a great idea and very much could be done. It's a possible way to expose a Flight SQL Producer for any JDBC compatible database.
We hadn't done this originally as we intended the Derby Flight SQL producer to be used purely as a platform for testing the FlightSQL stack (that's why it sits in the test part of the codebase). On Tue, Feb 22, 2022 at 1:59 PM Gavin Ray <ray.gavi...@gmail.com> wrote: > Hello all, > > Perhaps a bit of a dumb question, but going through the Flight codebase I > noticed this: > > https://github.com/apache/arrow/blob/5680d209fd870f99134e2d7299b47acd90fabb8e/java/flight/flight-sql/src/test/java/org/apache/arrow/flight/sql/example/FlightSqlExample.java#L182-L183 > > public class FlightSqlExample implements FlightSqlProducer, AutoCloseable { > private static final String DATABASE_URI = "jdbc:derby:target/derbyDB"; > > I wanted to ask whether there was any reason someone couldn't abstract this > into a > "FlightSqlJDBCServer" that took a JDBC connection URI and exposed a > FlightSQL server over it. > > This would in theory give any language that has a FlightSQL client library > the ability to > re-use existing JDBC drivers, albeit at a bit of a performance cost right? > > Seems like it could be useful, but I thought there might be a reason why > someone hadn't done this (Chesterton's Fence) > Thank you =) > > Gavin Ray. > -- *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.
