The final branch is ready for review: 
https://github.com/apache/arrow-adbc/pull/971

I'll start the vote later this week.

On Fri, Jul 28, 2023, at 10:04, David Li wrote:
> A late update here: I've merged most of the proposed changes and 
> implementations for ADBC 1.1.0 into a branch [1]. The remaining work is 
> to finish up the C++ implementation and Python bindings, after which 
> I'll propose a vote, hopefully in the next 2 weeks. Any feedback on the 
> API proposal so far would be much appreciated (diff against main at 
> [2]; focus on adbc.h, go/adbc/adbc.go, and java/adbc-core). 
>
> I don't expect 1.1.0 to include C# or Rust, but I think this is OK as 
> they are still being brought up regardless.
>
> [1]: https://github.com/apache/arrow-adbc/tree/spec-1.1.0
> [2]: https://github.com/apache/arrow-adbc/compare/main...spec-1.1.0
>
> On Wed, Jun 21, 2023, at 14:00, David Li wrote:
>> Two updates here:
>>
>> - We've merged the C# and Rust PRs. They were not in the recent 
>> release, but are in the source tree, and I hope we can continue 
>> iterating on them. (A few contributors have been actively working on 
>> C#.)
>> - A second PR [1] has been filed that proposes new APIs for ADBC around 
>> metadata and statistics. Any comments there would be much appreciated! 
>> (Only C/C++ is sketched, they will be ported to Go/Java once there's a 
>> rough consensus.)
>>
>> [1]: https://github.com/apache/arrow-adbc/pull/765
>>
>> On Thu, May 25, 2023, at 14:50, David Li wrote:
>>> We originally agreed to treat the ADBC APIs as a specification, 
>>> requiring votes for updates to the specification.
>>>
>>> To that end, this PR [1] proposes new APIs for ADBC to cover various 
>>> gaps identified, to clarify some language, and to make things 
>>> consistent with the Flight SQL proposals discussed earlier [2]. In 
>>> addition, assuming the ArrowDeviceArray proposal [3] is accepted the PR 
>>> will be updated again to support the new types.
>>>
>>> The definitions are backwards compatible, with some messiness in C/C++ 
>>> around one struct. The plan is to merge the new APIs into a branch, 
>>> then merge implementations into that branch, before bringing things 
>>> back for a final review/vote.
>>>
>>> Any feedback would be welcome. 
>>>
>>> Incidentally: proposals for C# [4] and Rust [5] now exist. I'd like to 
>>> treat both of them as 'experimental', in the sense that we will merge 
>>> them without formal vote for now while we implement the APIs, so we can 
>>> work out any revisions before the formal vote.
>>>
>>> [1]: https://github.com/apache/arrow-adbc/pull/692
>>> [2]: https://lists.apache.org/thread/247z3t06mf132nocngc1jkp3oqglz7jp
>>> [3]: https://lists.apache.org/thread/o2hsw7o1gm3qgw5z51rmz6zqxh0p7bvk
>>> [4]: https://github.com/apache/arrow-adbc/pull/697
>>> [5]: https://github.com/apache/arrow-adbc/pull/478
>>>
>>> -David

Reply via email to