t;> Hello again,>> Quick update: the C++, C#, Go and Java implementations now all> participate in C Data Interface integration testing.>> (this helped us fix a few interoperability bugs, and add deterministic> releasing of imported data in Go)>> Arrow Rust does not p
UNSUBSCRIBE
BAJARSE
ANFOSGRIFIAD
ОТПИШИ
HLOKOMELA
On Thu, Oct 19, 2023 at 9:56 AM Antoine Pitrou wrote:
>
> Hello again,
>
> Quick update: the C++, C#, Go and Java implementations now all
> participate in C Data Interface integration testing.
>
> (this helped us fix a
>
>
> UNSUBSCRIBE
>
Nice work!
Neal
On Thu, Oct 19, 2023 at 4:01 PM Antoine Pitrou wrote:
>
> Hello again,
>
> Quick update: the C++, C#, Go and Java implementations now all
> participate in C Data Interface integration testing.
>
> (this helped us fix a few interoperability bugs,
Hello again,
Quick update: the C++, C#, Go and Java implementations now all
participate in C Data Interface integration testing.
(this helped us fix a few interoperability bugs, and add deterministic
releasing of imported data in Go)
Arrow Rust does not participate yet, but given how
Thank you for setting this up! I look forward to adding nanoarrow as
soon as time allows.
Cheers,
-dewey
On Tue, Sep 26, 2023 at 9:48 AM Antoine Pitrou wrote:
>
>
> Hello,
>
> We have added some infrastructure for integration testing of the C Data
> Interface between Arrow i
Hello,
We have added some infrastructure for integration testing of the C Data
Interface between Arrow implementations. We are now testing the C++ and
Go implementations, but the goal in the future is for all major
implementations to be tested there (perhaps including nanoarrow).
- PR
a
> Interface, I've put together a small proposal for developing the
> integration testing for the C Data interface. For the most part it's an
> extension of Archery and the way Archery's integration testing works. I've
> put it into a Google doc and anyone with the link[1] should be
Hey all! Given various discussions about our testing and the C Data
Interface, I've put together a small proposal for developing the
integration testing for the C Data interface. For the most part it's an
extension of Archery and the way Archery's integration testing works. I've
put
Neville Dipale
> wrote:
>
> > Good day Arrow devs,
> >
> > I've spent a few evenings looking into the issues that we're experiencing
> > with Rust integration testing.
> > In summary, none of our tests pass (zero batch doesn't count :) ).
> > This is mai
at 1:03 PM Neville Dipale
wrote:
> Good day Arrow devs,
>
> I've spent a few evenings looking into the issues that we're experiencing
> with Rust integration testing.
> In summary, none of our tests pass (zero batch doesn't count :) ).
> This is mainly because of changes from the
Good day Arrow devs,
I've spent a few evenings looking into the issues that we're experiencing
with Rust integration testing.
In summary, none of our tests pass (zero batch doesn't count :) ).
This is mainly because of changes from the legacy padding in the 0.15.0
release, which we never made
Neville Dipale created ARROW-8883:
-
Summary: [Rust] [Integration Testing] Disable unsupported tests
Key: ARROW-8883
URL: https://issues.apache.org/jira/browse/ARROW-8883
Project: Apache Arrow
Andy Grove created ARROW-8859:
-
Summary: [Rust] [Integration Testing] Implement --quiet / verbose
correctly
Key: ARROW-8859
URL: https://issues.apache.org/jira/browse/ARROW-8859
Project: Apache Arrow
Andy Grove created ARROW-8856:
-
Summary: [Rust] [Integration Testing] Reading types other than
record batches not yet supported
Key: ARROW-8856
URL: https://issues.apache.org/jira/browse/ARROW-8856
Andy Grove created ARROW-8855:
-
Summary: [Rust] [Integration Testing] data type Date32(Day) not
supported
Key: ARROW-8855
URL: https://issues.apache.org/jira/browse/ARROW-8855
Project: Apache Arrow
Andy Grove created ARROW-8854:
-
Summary: [Rust] [Integration Testing] Show output from
arrow-json-integration-test
Key: ARROW-8854
URL: https://issues.apache.org/jira/browse/ARROW-8854
Project: Apache
Andy Grove created ARROW-8853:
-
Summary: [Rust] [Integration Testing] Enable Flight tests
Key: ARROW-8853
URL: https://issues.apache.org/jira/browse/ARROW-8853
Project: Apache Arrow
Issue Type
Andy Grove created ARROW-8835:
-
Summary: [Rust] Implement arrow-stream-to-file for integration
testing
Key: ARROW-8835
URL: https://issues.apache.org/jira/browse/ARROW-8835
Project: Apache Arrow
Andy Grove created ARROW-8834:
-
Summary: [Rust] Implement arrow-file-to-stream for integration
testing
Key: ARROW-8834
URL: https://issues.apache.org/jira/browse/ARROW-8834
Project: Apache Arrow
Andy Grove created ARROW-8827:
-
Summary: [Integration Testing] Initial skeleton for Rust
integration tests
Key: ARROW-8827
URL: https://issues.apache.org/jira/browse/ARROW-8827
Project: Apache Arrow
Andy Grove created ARROW-8807:
-
Summary: [Docs] Integration testing instructions for base docker
image are incorrect
Key: ARROW-8807
URL: https://issues.apache.org/jira/browse/ARROW-8807
Project: Apache
On Thu, Mar 5, 2020 at 8:44 PM Micah Kornfield
wrote:
> Hi Neal,
> Sorry for the late reply.
>
> Unsigned integers in Java was resolved via
> https://github.com/apache/arrow/pull/4432
>
>
Thanks, I've updated the spreadsheet to reflect that.
> We might want to separate out Dense/Sparse union
Hi Neal,
Sorry for the late reply.
Unsigned integers in Java was resolved via
https://github.com/apache/arrow/pull/4432
We might want to separate out Dense/Sparse union testing into their own
issues.
Thanks,
Micah
On Fri, Feb 21, 2020 at 2:12 PM Neal Richardson
wrote:
> Thanks, I've marked
Thanks, I've marked that as not required for 1.0 (and added a legend to the
bottom of the table). Anything else that needs to be added or reclassified?
Neal
On Fri, Feb 21, 2020 at 12:19 AM Antoine Pitrou wrote:
>
> Hi,
>
> I don't think float16 support is required for 1.0.
> On the C++ side
Hi,
I don't think float16 support is required for 1.0.
On the C++ side at least, it will require integrating a dedicated
library (probably in other languages as well).
Regards
Antoine.
Le 21/02/2020 à 00:33, Neal Richardson a écrit :
> Hi all,
> To help us reach 1.0 with as complete and
Hi all,
To help us reach 1.0 with as complete and thoroughly tested implementations
of the Arrow format, I've surveyed our integration test suite and open
issues and collected information here:
https://docs.google.com/spreadsheets/d/1Yu68rn2XMBpAArUfCOP9LC7uHb06CQrtqKE5vQ4bQx4/edit#gid=782909347
Paddy Horan created ARROW-6109:
--
Summary: [Integration] Docker image for integration testing can't
be built on windows
Key: ARROW-6109
URL: https://issues.apache.org/jira/browse/ARROW-6109
Project
Wes McKinney created ARROW-5405:
---
Summary: [Documentation] Move integration testing documentation to
Sphinx docs, add instructions for JavaScript
Key: ARROW-5405
URL: https://issues.apache.org/jira/browse/ARROW
Wes McKinney created ARROW-5312:
---
Summary: [C++] Move JSON integration testing utilities to
arrow/testing and libarrow_testing.so
Key: ARROW-5312
URL: https://issues.apache.org/jira/browse/ARROW-5312
David Li created ARROW-5143:
---
Summary: [Flight] Enable integration testing of batches with
dictionaries
Key: ARROW-5143
URL: https://issues.apache.org/jira/browse/ARROW-5143
Project: Apache Arrow
David Li created ARROW-4575:
---
Summary: Add Python Flight implementation to integration testing
Key: ARROW-4575
URL: https://issues.apache.org/jira/browse/ARROW-4575
Project: Apache Arrow
Issue
t
> > > > >> (I'm
> > > > >> > >> sure this is going to take quite a while though so don't want
> > to
> > > get
> > > > >> > >> anyones hopes up too much). For anyon
Andy.
> > > >> > >>
> > > >> > >>
> > > >> > >> On Sat, May 19, 2018 at 4:05 PM Wes McKinney <
> > wesmck...@gmail.com>
> > > >> wrote:
> > > >> > >>
> > > >&
wesmck...@gmail.com>
> > >> wrote:
> > >> > >>
> > >> > >>> Sorry to hear, it's a bit of a rough situation with Flatbuffers
> and
> > >> > >>> Rust. One possibility is to build an interface to the
> Flatbuf
re header-only like C++ and if that makes things any
> >> easier
> >> > >>> for you.
> >> > >>>
> >> > >>> If you defined an API in Rust for reading and writing the Arrow
> >> > >>> metadata that does not expos
>> > >>> for you.
>> > >>>
>> > >>> If you defined an API in Rust for reading and writing the Arrow
>> > >>> metadata that does not expose any Flatbuffers-specific details, then
>> > >>> once there is a produc
mentation details could be swapped out without disruption.
> > >>>
> > >>> > my recent attempts at contacting the author have been unsuccessful
> > >>>
> > >>> Have you e-mailed the author directly or only pings on GitHub? Pings
> &
>>> Have you e-mailed the author directly or only pings on GitHub? Pings
> >>> may not be making it to their inbox.
> >>>
> >>> Appreciate your efforts on this; I think we'll see a lot more work in
> >>> data processing in Rust in the coming yea
; I think we'll see a lot more work in
>>> data processing in Rust in the coming years.
>>>
>>> - Wes
>>>
>>> On Fri, May 18, 2018 at 9:21 AM, Andy Grove
>>> wrote:
>>> > Hi,
>>> >
>>> > Now that the refactor
Chao Sun created ARROW-3690:
---
Summary: [Rust] add Rust to integration testing
Key: ARROW-3690
URL: https://issues.apache.org/jira/browse/ARROW-3690
Project: Apache Arrow
Issue Type: Test
nk we'll see a lot more work in
>> data processing in Rust in the coming years.
>>
>> - Wes
>>
>> On Fri, May 18, 2018 at 9:21 AM, Andy Grove
>> wrote:
>> > Hi,
>> >
>> > Now that the refactor I've been working on has been merged, the
M, Andy Grove wrote:
> > Hi,
> >
> > Now that the refactor I've been working on has been merged, the next
> > priority for me personally with the Rust implementation is getting IPC
> and
> > integration testing working.
> >
> > Unfortunately the of
ndy Grove <andygrov...@gmail.com> wrote:
> Hi,
>
> Now that the refactor I've been working on has been merged, the next
> priority for me personally with the Rust implementation is getting IPC and
> integration testing working.
>
> Unfortunately the official Flatbuffers Rus
Hi,
Now that the refactor I've been working on has been merged, the next
priority for me personally with the Rust implementation is getting IPC and
integration testing working.
Unfortunately the official Flatbuffers Rust version is not available yet
and my recent attempts at contacting
Wes McKinney created ARROW-1502:
---
Summary: [JS] Define code entry point for integration testing
Key: ARROW-1502
URL: https://issues.apache.org/jira/browse/ARROW-1502
Project: Apache Arrow
Wes McKinney created ARROW-941:
--
Summary: [Docs] Improve "cold start" integration testing
instructions
Key: ARROW-941
URL: https://issues.apache.org/jira/browse/ARROW-941
Project: Ap
Wes McKinney created ARROW-921:
--
Summary: Add scripts to facilitate integration testing between
revisions of the codebase
Key: ARROW-921
URL: https://issues.apache.org/jira/browse/ARROW-921
Project
Wes McKinney created ARROW-620:
--
Summary: [C++] Add date/time support to JSON reader/writer for
integration testing
Key: ARROW-620
URL: https://issues.apache.org/jira/browse/ARROW-620
Project: Apache
CLI tool to read an Arrow file and write it out (for
> integration testing)
> ---
>
> Key: ARROW-310
> URL: https://issues.apache.org/jira/browse/ARROW-310
>
]
> Implement Arrow Echo server for integration testing
> ---
>
> Key: ARROW-506
> URL: https://issues.apache.org/jira/browse/ARROW-506
> Project: Apache Arrow
> Issue Type: Task
Nong Li created ARROW-506:
-
Summary: Implement Arrow Echo server for integration testing
Key: ARROW-506
URL: https://issues.apache.org/jira/browse/ARROW-506
Project: Apache Arrow
Issue Type: Task
Wes McKinney created ARROW-310:
--
Summary: [Java] Create CLI tool to read an Arrow file and write it
out (for integration testing)
Key: ARROW-310
URL: https://issues.apache.org/jira/browse/ARROW-310
53 matches
Mail list logo
