+1 from me, with the same caveat about the Go integration tests.
Verified sources (C++, Python, Java, integration), wheels, and binaries on
Ubuntu 18.04.
-David
On Sun, Jul 25, 2021, at 13:59, Matt Topol wrote:
> This is the Jira issue for the go tags
>
>
This is the Jira issue for the go tags
https://issues.apache.org/jira/browse/ARROW-8621
I'm not familiar enough with the release scripts to volunteer to do it
myself unfortunately.
On Sun, Jul 25, 2021, 1:54 PM Benjamin Kietzman wrote:
> Thanks for that clarification, Matt. Is there a Jira
Thanks for that clarification, Matt. Is there a Jira for getting tags right
for Go?
On Sun, Jul 25, 2021, 12:51 Matt Topol wrote:
> Because the release process is still not tagging the releases appropriately
> for Go, I don't think it's necessary to wait because as soon as this is
> merged to
I merged the fix, I marked the JIRA fix version 6.0.0
On Sun, Jul 25, 2021 at 10:51 AM Matt Topol wrote:
> Because the release process is still not tagging the releases appropriately
> for Go, I don't think it's necessary to wait because as soon as this is
> merged to master it will be
I think if all reference implementations are doing this the same way we
should update the docs and I don't think a vote is necessary.
On Sun, Jul 25, 2021 at 10:27 AM David Li wrote:
> Hey Nate,
>
> Good catch. I would say it was intentional to use an IPC message (while
> the length is
Hey Nate,
Good catch. I would say it was intentional to use an IPC message (while the
length is redundant, it also contains the metadata version and custom
metadata), and the comment is a little vague. I'm not sure if we need a vote to
update this since it is changing files in the format dir.
Because the release process is still not tagging the releases appropriately
for Go, I don't think it's necessary to wait because as soon as this is
merged to master it will be available for consumption via go get -u
For go, tags need to be added with the release in the form of
"go/arrow/v5.0.0"
+1 I AGREE
On Sun, Jul 25, 2021 at 10:04 AM Krisztián Szűcs
wrote:
> On Sat, Jul 24, 2021 at 6:46 PM Matt Topol wrote:
> >
> > So, looking at the error message in the Go integration tests and looking
> at
> > the stack trace, I was able to confirm the bug. I'm not sure why it
> showed
> > up
On Sat, Jul 24, 2021 at 6:46 PM Matt Topol wrote:
>
> So, looking at the error message in the Go integration tests and looking at
> the stack trace, I was able to confirm the bug. I'm not sure why it showed
> up in that run but not subsequent / reproducible but the issue comes down
> to the
