Thanks all, I agree with validating each record batch independently. I made
https://issues.apache.org/jira/browse/ARROW-7966 to ensure this, and that
will hopefully iron out any kinks in the different implementations.
Thanks,
Bryan
On Wed, Feb 26, 2020 at 3:13 PM Wes McKinney wrote:
> I agree
I agree with independent validation.
On Tue, Feb 25, 2020 at 2:55 PM David Li wrote:
>
> Hey Bryan,
>
> Thanks for looking into this issue. I would vote that we should
> validate each batch independently, so we can catch issues related to
> the structure of the data and not just the content. C++
Hey Bryan,
Thanks for looking into this issue. I would vote that we should
validate each batch independently, so we can catch issues related to
the structure of the data and not just the content. C++ doesn't do any
detection of empty batches per se, but on both ends it reads all the
data into a
While looking into Null type testing for ARROW-7899, a couple small issues
came up regarding Flight integration testing with empty batches (row count
== 0) that could be worked out with a quick discussion. It seems there is a
small difference between the C++ and Java Flight servers when there are
