Re: Debugging Gandiva failures in python CI tests

I missed mentioning this. The repro requires my changes for decimal (in the PR). https://github.com/apache/arrow/pull/2942 > On Jan 6, 2019, at 4:23 PM, Ravindra Pindikura wrote: > > > >> On Jan 6, 2019, at 3:38 PM, Antoine Pitrou >

[jira] [Created] (ARROW-4175) [GLib] Add support for decimal compare operators

Kouhei Sutou created ARROW-4175: --- Summary: [GLib] Add support for decimal compare operators Key: ARROW-4175 URL: https://issues.apache.org/jira/browse/ARROW-4175 Project: Apache Arrow Issue

[jira] [Created] (ARROW-4174) [Ruby] Add support for building composite array from raw Ruby objects

Kouhei Sutou created ARROW-4174: --- Summary: [Ruby] Add support for building composite array from raw Ruby objects Key: ARROW-4174 URL: https://issues.apache.org/jira/browse/ARROW-4174 Project: Apache

[jira] [Created] (ARROW-4173) JIRA library name is wrong in error message of dev/merge_arrow_pr.py

Kouhei Sutou created ARROW-4173: --- Summary: JIRA library name is wrong in error message of dev/merge_arrow_pr.py Key: ARROW-4173 URL: https://issues.apache.org/jira/browse/ARROW-4173 Project: Apache

[jira] [Created] (ARROW-4172) [Rust] more consistent naming in array builders

Chao Sun created ARROW-4172: --- Summary: [Rust] more consistent naming in array builders Key: ARROW-4172 URL: https://issues.apache.org/jira/browse/ARROW-4172 Project: Apache Arrow Issue Type:

[jira] [Created] (ARROW-4171) [Rust] fix parquet crate release version

Chao Sun created ARROW-4171: --- Summary: [Rust] fix parquet crate release version Key: ARROW-4171 URL: https://issues.apache.org/jira/browse/ARROW-4171 Project: Apache Arrow Issue Type: Bug

[jira] [Created] (ARROW-4170) [CI/Rust] Create separate CI job for parquet crate

Chao Sun created ARROW-4170: --- Summary: [CI/Rust] Create separate CI job for parquet crate Key: ARROW-4170 URL: https://issues.apache.org/jira/browse/ARROW-4170 Project: Apache Arrow Issue Type:

Re: [Rust] crate versions and release process

OK, I don't want to add much extra work to the release process. Let's use the single version for now then and perhaps revisit this in future. On Sun, Jan 6, 2019 at 10:41 AM Wes McKinney wrote: > On Sun, Jan 6, 2019 at 12:18 PM Chao Sun wrote: > > > > I think version number (in terms of

Re: [Rust] [DISCUSS] Donate DataFusion to Arrow project

Cool! On Sun, Jan 6, 2019 at 1:52 PM Andy Grove wrote: > I'm starting a new thread for this discussion (this was previously > discussed in the Rust Roadmap thread). > > The reason I got involved with Arrow is that I have been working on > DataFusion[1] which is currently an in-process SQL

[Rust] [DISCUSS] Donate DataFusion to Arrow project

I'm starting a new thread for this discussion (this was previously discussed in the Rust Roadmap thread). The reason I got involved with Arrow is that I have been working on DataFusion[1] which is currently an in-process SQL query engine on top of Arrow. It allows queries to be executed against

Re: [Rust] crate versions and release process

On Sun, Jan 6, 2019 at 12:18 PM Chao Sun wrote: > > I think version number (in terms of major.minor.fix) does carry a meaning > and IMO it is less desirable to apply a single value for all the > sub-modules. Ideally all these should be marching at the same speed but in > reality that may not be

Re: [Rust] crate versions and release process

I think version number (in terms of major.minor.fix) does carry a meaning and IMO it is less desirable to apply a single value for all the sub-modules. Ideally all these should be marching at the same speed but in reality that may not be the case. Besides critical bug/security fixes, at some point

Re: Enabling an installation path for Arrow R users

hi, On Sun, Jan 6, 2019 at 11:13 AM Jeroen Ooms wrote: > > On Sun, Jan 6, 2019 at 5:39 PM Wes McKinney wrote: > > > > hi Jeroen, > > > > On Sun, Jan 6, 2019 at 10:28 AM Jeroen Ooms wrote: > > > > > > On 2019/01/02 17:08:58, Wes McKinney wrote: > > > > hi folks,> > > > > > > > > With 0.12

Re: Enabling an installation path for Arrow R users

On Sun, Jan 6, 2019 at 5:39 PM Wes McKinney wrote: > > hi Jeroen, > > On Sun, Jan 6, 2019 at 10:28 AM Jeroen Ooms wrote: > > > > On 2019/01/02 17:08:58, Wes McKinney wrote: > > > hi folks,> > > > > > > With 0.12 around the corner and significant progress on the R bindings> > > > project

Re: Enabling an installation path for Arrow R users

hi Jeroen, On Sun, Jan 6, 2019 at 10:28 AM Jeroen Ooms wrote: > > On 2019/01/02 17:08:58, Wes McKinney wrote: > > hi folks,> > > > > With 0.12 around the corner and significant progress on the R bindings> > > project (sufficient for Spark integration [1]), I am wondering how> > > everyday R

Re: Enabling an installation path for Arrow R users

On 2019/01/02 17:08:58, Wes McKinney wrote: > hi folks,> > > With 0.12 around the corner and significant progress on the R bindings> > project (sufficient for Spark integration [1]), I am wondering how> > everyday R users are going to be able to install the software> > respectively on Linux,

[jira] [Created] (ARROW-4169) [Rust] Set up cargo bench for running benchmarks

Andy Grove created ARROW-4169: - Summary: [Rust] Set up cargo bench for running benchmarks Key: ARROW-4169 URL: https://issues.apache.org/jira/browse/ARROW-4169 Project: Apache Arrow Issue Type:

[jira] [Created] (ARROW-4168) [GLib] Use property to keep GArrowDataType passed in garrow_field_new()

Yosuke Shiro created ARROW-4168: --- Summary: [GLib] Use property to keep GArrowDataType passed in garrow_field_new() Key: ARROW-4168 URL: https://issues.apache.org/jira/browse/ARROW-4168 Project: Apache

Re: [Rust] crate versions and release process

This is definitely possible for Apache projects. Currently we still have two releases: "Arrow without JS" and "Arrow JS". We can have separate release votes for security and small fixes for subcrates. There are mainly two things that "limit us": 1. We still need to do the release votes (there

Re: Arrow Rust roadmapping [was Re: [Gandiva] Representing logical query plans in protobuf]

Hello Andy, one thing that we had in discussions in the past and also opened me up a bit to the parquet-cpp merge is that merging code into a repo doesn't mean that it will reside always there. Apache has the infrastructure and guidelines to split a part of a project into a separate one. This

Re: [Rust] crate versions and release process

The main question is: do we want independent reales (for security and severe bugs) or not? If so, what about the following versioning scheme: Major.Minor.Fix Major and minor are in-sync for all languages and libraries/crates and can be featured using in blog posts and other channels. Fix

[jira] [Created] (ARROW-4167) [Gandiva] switch to arrow/util/variant

Pindikura Ravindra created ARROW-4167: - Summary: [Gandiva] switch to arrow/util/variant Key: ARROW-4167 URL: https://issues.apache.org/jira/browse/ARROW-4167 Project: Apache Arrow Issue

Re: Debugging Gandiva failures in python CI tests

> On Jan 6, 2019, at 3:38 PM, Antoine Pitrou wrote: > > > Can you tell me how to reproduce? I'll take a look on Monday. Thank you. I used the following steps to repro (on ubuntu 14) : 1. conda section to setup the python environment

Re: Debugging Gandiva failures in python CI tests

Can you tell me how to reproduce? I'll take a look on Monday. Regards Antoine. Le 06/01/2019 à 10:24, Ravindra Pindikura a écrit : > > >> On Dec 29, 2018, at 8:03 PM, Ravindra Pindikura wrote: >> >> >> >>> On Dec 28, 2018, at 1:38 AM, Wes McKinney wrote: >>> >>> You might have to wait

Re: Debugging Gandiva failures in python CI tests

> On Dec 29, 2018, at 8:03 PM, Ravindra Pindikura wrote: > > > >> On Dec 28, 2018, at 1:38 AM, Wes McKinney wrote: >> >> You might have to wait for Antoine's help after the holidays. In the >> meantime: do you get the error when building both with gcc 4.8/4.9 and >> clang-6.0? I did a bit