lidavidm commented on PR #1717: URL: https://github.com/apache/arrow-adbc/pull/1717#issuecomment-2051326734
> > Also, one final thing 😅 is this using the REST API or the gRPC API? The REST API would not have problems if you want to keep it in C++. (Though I may say, let's try to use Nanoarrow instead of Arrow C++ in that case to try to keep binary sizes down.) > > It uses REST API to start the query job and receives the result table using gRPC API because the REST API can only output plain JSON format for the result table. 😞 That...is fun. > What would that entail? I am not worried about package ownership, license, and so on. I would be glad to transfer all of those to Apache. Plus having us linked and mentioned in the official docs would be fantastic. My concern is only with the versioning and issues tracker (maintenance) if they are all part of a single monorepo? What are your thoughts on this? We _most likely_ need a IP transfer to satisfy Apache since it is a substantial amount of code developed outside Apache. If the both of you are the only contributors so far, then it would just amount to signing some paperwork, essentially. You wouldn't necessarily have to join the monorepo; some implementations are in separate repos (Julia, Rust - though those are completely independent, standalone implementations), and I think it would be worth discussing where Elixir/Erlang would fall. You could join [dev@](https://arrow.apache.org/community/) and inquire to get a better feel. Also, even in the monorepo, we are talking about decoupling versioning (though still doing releases as a batch to save release manager effort). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
