0 (binding) - imo there is some unclarity over what is expected to be passed over the C streaming interface - an Array or a StructArray.
I think the spec claims the former, but the C++ implementation (which I assume is the reference here) expects the latter [1]. Would it be possible to clarify this on either end so we do not clone the spec and/or reference implementation with this unclarity? +1 if we are voting on formalizing the spec as written, and consider ARROW-15747 as something for C++/Python to improve upon. In other words, I favor that the C stream interface is aligned with the C data interface with respect to what it consumes (arbitrary arrays). [1] https://issues.apache.org/jira/browse/ARROW-15747 Best, Jorge On Wed, Jun 8, 2022 at 8:29 PM Antoine Pitrou <anto...@python.org> wrote: > > +1 (binding) > > > Le 08/06/2022 à 20:15, Will Jones a écrit : > > Hi, > > > > Given all feedback to discussion [1] has been positive, I would like to > > propose marking the C Stream Interface as stable. > > > > I have prepared PRs in apache/arrow [2] and apache/arrow-rs [3] to remove > > all "experimental" markers from the interface and update the support grid > > for the interface. > > > > Only votes from PMC members are binding, but all members of the community > > are encouraged to provide input and vote with "(non-binding)". The vote > > will run for at least 72 hours. > > > > [ ] +1 Remove all "experimental" marks from C Streaming Interface > > [ ] +0 > > [ ] -1 Keep "experimental" warnings on C Streaming Interface > > > > [1] https://lists.apache.org/thread/0y604o9s3wkyty328wv8d21ol7s40q55 > > [2] https://github.com/apache/arrow/pull/13345 > > [3] https://github.com/apache/arrow-rs/pull/1821 > > >
