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.
