On Fri, 19 Aug 2022 14:09:44 -0400 "David Li" <lidav...@apache.org> wrote: > Since it's been a while, I'd like to give an update. There are also a few > questions I have around distribution. > > Currently: > - Supported in C, Java, and Python. > - For C/Python, there are basic drivers wrapping Flight SQL and SQLite, with > a draft of a libpq (Postgres) driver (using nanoarrow). > - For Java, there are drivers wrapping JDBC and Flight SQL. > - For Python, there's low-level bindings to the C API, and the DBAPI > interface on top of that (+a few extension methods resembling > DuckDB/Turbodbc). > > There's drafts of integration with Ibis [1], DBI (R), and DuckDB. (I'd like > to thank Hannes and Kirill for their comments, as well as Antoine, Dewey, and > Matt here.) > > I'd like to have this as part of 10.0.0 in some fashion. However, I'm not > sure how we would like to handle packaging and distribution. In particular, > there are several sub-components for each language (the driver manager + the > drivers), increasing the work. Any thoughts here?
Sorry, forgot to answer here. But I think your question is too broadly formulated. It probably deserves a case-by-case discussion, IMHO. > I'm also wondering how we want to handle this in terms of specification - I > assume we'd consider the core header file/Java interfaces a spec like the C > Data Interface/Flight RPC, and vote on them/mirror them into the format/ > directory? That sounds like the right way to me indeed. Regards Antoine.
