+1 (binding)
On Mon, Jul 18, 2022 at 5:20 PM L. C. Hsieh wrote:
> +1 (non-binding)
>
> Thanks.
>
> On Mon, Jul 18, 2022 at 8:57 AM QP Hou wrote:
> >
> > +1 (binding)
> >
> > On Mon, Jul 18, 2022 at 8:55 AM Andrew Lamb
> wrote:
> > >
> > > Hello,
> > >
> > > This vote is to determine if the Arr
Hi,
I've released 8.0.1:
* I've published
https://dist.apache.org/repos/dist/release/arrow/arrow-8.0.1/
* I've pushed the
https://github.com/apache/arrow/releases/tag/go%2Fv8.0.1
tag
* I've made the "8.0.1" version on JIRA "released":
https://issues.apache.org/jira/projects/
Hi,
I've released 7.0.1:
* I've published
https://dist.apache.org/repos/dist/release/arrow/arrow-7.0.1/
* I've pushed the
https://github.com/apache/arrow/releases/tag/go%2Fv7.0.1
tag
* I've made the "7.0.1" version on JIRA "released":
https://issues.apache.org/jira/projects/
Hi,
I've released 6.0.2:
* I've published
https://dist.apache.org/repos/dist/release/arrow/arrow-6.0.2/
* I've pushed the
https://github.com/apache/arrow/releases/tag/go%2Fv6.0.2
tag
* I've made the "6.0.2" version on JIRA "released":
https://issues.apache.org/jira/projects/
Hi,
The vote carries with 3 +1 binding votes, 1 +1 non-binding
vote, 1 +0 binding vote and 1 +0 binding vote.
I'll publish this as 7.0.1.
Thanks,
--
kou
In <20220715.061039.1868304737470784647@clear-code.com>
"[VOTE] Release Apache Arrow 7.0.1 - RC0" on Fri, 15 Jul 2022 06:10:39 +0900
(
Hi Matthew,
Thanks for letting us know your opinion. OK. We'll release
as-is.
Thanks,
--
kou
In
"Re: [VOTE] Release Apache Arrow 7.0.1 - RC0" on Mon, 18 Jul 2022 20:32:53
-0400,
Matt Topol wrote:
> As long as running `go install` / `go build` works when run against go
> version 1.16, wh
As long as running `go install` / `go build` works when run against go
version 1.16, which as far as I'm aware is the version that is run for our
current CI, then there shouldn't be any issues with the other extraneous
package version bumps.
In my opinion, it's fine to release as-is.
--Matt
On M
Hi,
The vote carries with 4 +1 binding votes and 2 +1
non-binding votes.
I'll publish this as 8.0.1.
Thanks,
--
kou
In <20220715.061057.1116573445635493266@clear-code.com>
"[VOTE] Release Apache Arrow 8.0.1 - RC0" on Fri, 15 Jul 2022 06:10:57 +0900
(JST),
Sutou Kouhei wrote:
> Hi,
>
Hi,
The vote carries with 4 +1 binding votes and 2 +1
non-binding votes.
I'll publish this as 6.0.2.
Thanks,
--
kou
In <20220715.061031.728260673372395082@clear-code.com>
"[VOTE] Release Apache Arrow 6.0.2 - RC0" on Fri, 15 Jul 2022 06:10:31 +0900
(JST),
Sutou Kouhei wrote:
> Hi,
>
Hi Matthew,
If you have any opinion about this as a Go developer, please
let us know. If you don't have any opinion, we will release
this as-is.
Thanks,
--
kou
In
"Re: [VOTE] Release Apache Arrow 7.0.1 - RC0" on Mon, 18 Jul 2022 11:56:48
+0200,
Jacob Wujciak wrote:
> I would lean towar
Hi Valentyn,
Just to make sure, is this Flight or Flight SQL? I ask since Flight itself does
not have a notion of transactions in the first place. I'm also curious what the
intended target client application is.
Not being familiar with graph databases myself, I'll try to give some comments…
La
Hi All,
I'm investigating the possibility of using Arrow Flight with graph
databases, and exploring how to enable Arrow Flight endpoint in Apache
Tinkerpop Gremlin server.
Now graph databases use several incompatible protocols that make it
difficult to use and spread the technology.
A common feat
Ah yeah, that's correct. Arrow goes through significant effort to hide the
generated files as much as it can to try to avoid conflicts if someone were
to dynamically link both Arrow and something else that uses Substrait
together. You also won't find the Substrait headers be exposed by the Arrow
in
Thanks both. This appears to work!
With regard to linking, I also have libsubstrait.a under build/debug, but
not in dist/lib - I suppose maybe the substrait classes are statically
linked into libarrow.so?
Li
On Mon, Jul 18, 2022 at 3:19 PM Jeroen van Straten <
jeroen.van.stra...@gmail.com> wrote
I think the SHA in versions.txt is for the tarball specifically (prior to
decompression), so I think it'll complain if you set it to a repository
directory instead.
Jeroen
On Mon, 18 Jul 2022 at 20:40, Yaron Gvili wrote:
> ARROW_SUBSTRAIT_URL works for both a *.tar.gz file and a repository
> d
ARROW_SUBSTRAIT_URL works for both a *.tar.gz file and a repository directory.
In my experience, there is no need to also set any sha256-related setting.
Yaron.
From: Li Jin
Sent: Monday, July 18, 2022 2:34 PM
To: dev@arrow.apache.org
Subject: Re: [C++] Questio
Thanks both! Let me try changing ARROW_SUBSTRAIT_URL. Should I set
ARROW_SUBSTRAIT_URL just to local substrait tarball or sth else?
On Mon, Jul 18, 2022 at 2:28 PM Yaron Gvili wrote:
> Hi Li,
>
> I was just writing this.
>
> AFAIK, currently the Arrow C++ build system does not take prebuilt
> Su
Hi Li,
I was just writing this.
AFAIK, currently the Arrow C++ build system does not take prebuilt Substrait
C++ classes. The usual way is rebuilding Arrow C++ with a custom Substrait
repository, which is done by setting ARROW_SUBSTRAIT_URL to a local Substrait
repository. You can download thi
Hi,
I'm not sure I completely understand what you're trying to do, but if lack
of internet access is the only problem, I think you should just be able to
override the URL it tries to download by setting the ARROW_SUBSTRAIT_URL
environment variable to some local file:// URL. I think it should work
+1 (non-binding)
Thanks.
On Mon, Jul 18, 2022 at 8:57 AM QP Hou wrote:
>
> +1 (binding)
>
> On Mon, Jul 18, 2022 at 8:55 AM Andrew Lamb wrote:
> >
> > Hello,
> >
> > This vote is to determine if the Arrow PMC is in favor of accepting the
> > donation of the Rust Object Store crate to arrow-rs.
Hello!
I am working on integrating the latest Arrow C++ into our internal build
system. Currently I am planning to build substrait C++ classes
independently and provide header locations and so files to the Arrow
Cmakefile - I wonder if that is a good approach? (We cannot download the
substrait tar
+1 (binding)
On Mon, Jul 18, 2022 at 8:55 AM Andrew Lamb wrote:
>
> Hello,
>
> This vote is to determine if the Arrow PMC is in favor of accepting the
> donation of the Rust Object Store crate to arrow-rs.
>
> We have previously discussed this topic [1] and [2].
>
> The proposed donation is at [3
Hello,
This vote is to determine if the Arrow PMC is in favor of accepting the
donation of the Rust Object Store crate to arrow-rs.
We have previously discussed this topic [1] and [2].
The proposed donation is at [3]. IP clearance work is underway in [4] and
[5]
The vote will be open for at lea
On Mon, Jul 18, 2022 at 2:35 AM Antoine Pitrou wrote:
>
>
> Le 18/07/2022 à 03:54, Wes McKinney a écrit :
> > This patch caused Parquet files written with 2.0.0 to be unreadable in
> > 3.0.0 onward
> >
> > https://github.com/apache/arrow/commit/ef0feb2c9c959681d8a105cbadc1ae6580789e69
> >
> > This
Hi,
We are still targeting next Monday 25th of July to start creating the first
release candidate for 9.0.0.
We are down to 37 Open/In progress issues and 6 blockers from 144 issues
and 7 blockers from a couple of weeks ago. Thanks everyone for the great
effort there!
This is the link to the con
I would lean towards backporting the fix too but I am not familiar with the
go ecosystem and this PR contains a bunch of version bumps, unsure if those
are required for the fix or were just added to the PR and if those are a
problem for go users of the existing 7.0.0 version?
On Fri, Jul 15, 2022
Le 18/07/2022 à 03:54, Wes McKinney a écrit :
This patch caused Parquet files written with 2.0.0 to be unreadable in
3.0.0 onward
https://github.com/apache/arrow/commit/ef0feb2c9c959681d8a105cbadc1ae6580789e69
This was reported on June 14 on dev@ and I git-bisected to the root cause:
https:/
27 matches
Mail list logo