[jira] [Created] (ARROW-1670) [Serialization] Speed up deserialization code path

Philipp Moritz created ARROW-1670: - Summary: [Serialization] Speed up deserialization code path Key: ARROW-1670 URL: https://issues.apache.org/jira/browse/ARROW-1670 Project: Apache Arrow

[jira] [Created] (ARROW-1669) [C++] Consider adding Abseil (Google C++11 standard library extensions) to toolchain

Wes McKinney created ARROW-1669: --- Summary: [C++] Consider adding Abseil (Google C++11 standard library extensions) to toolchain Key: ARROW-1669 URL: https://issues.apache.org/jira/browse/ARROW-1669

Re: Update on ARROW-1463, related subtasks and plan for testing and merging

Yes, that is the intention. Good that we all are on the same page. I will move the PR https://github.com/apache/arrow/pull/1164 to new branch. On Thu, Oct 12, 2017 at 11:20 AM, Li Jin wrote: > To make clear, I think it's fine to have Legacy Vectors in 0.8 as a >

Re: Update on ARROW-1463, related subtasks and plan for testing and merging

To make clear, I think it's fine to have Legacy Vectors in 0.8 as a deprecated API. On Thu, Oct 12, 2017 at 2:19 PM, Li Jin wrote: > Siddharth, > > For working off a branch, Wes has created https://github.com/apache/ > arrow/tree/java-vector-refactor that we can submit PR

Re: Update on ARROW-1463, related subtasks and plan for testing and merging

Siddharth, For working off a branch, Wes has created https://github.com/apache/arrow/tree/java-vector-refactor that we can submit PR to. For Legacy vectors, I think it's fine because it's really just a migration path to help Dremio to migrate to the new vectors. I don't think other users, i.e.,

Re: Update on ARROW-1463, related subtasks and plan for testing and merging

Thanks Bryan and Li. Yes, the goal is to get this (and the subsequent patches) merged to the new branch. Once it is stabilized from different aspects, we can move to master. I am not sure of the exact mechanics when we work off a different project branch and not master. Does that sound good?

Re: Update on ARROW-1463, related subtasks and plan for testing and merging

Thanks for the update Siddharth. From the Spark side of this, I definitely want to try to upgrade to the latest Arrow before the Spark 2.3 release but if it the refactor is too disruptive then others might get squeamish about upgrading. On the other hand, I don't think we should hold back on

[jira] [Created] (ARROW-1668) [JS] Draft roadmap / planning document for JS library development

Wes McKinney created ARROW-1668: --- Summary: [JS] Draft roadmap / planning document for JS library development Key: ARROW-1668 URL: https://issues.apache.org/jira/browse/ARROW-1668 Project: Apache Arrow

Re: Arrow sync call tomorrow 4 October @ 16:00 UTC

Sorry for the delay on posting meeting notes. I didn't keep very detailed notes but these are the topics that were mentioned: Attendees - Wes (Two Sigma) - 0.8.0 release planning - Release management issues - Li Jin (Two Sigma) - ARROW-1463 - Spark timestamp issues - ARROW-1425 -

[jira] [Created] (ARROW-1667) [GLib] Support Meson

Kouhei Sutou created ARROW-1667: --- Summary: [GLib] Support Meson Key: ARROW-1667 URL: https://issues.apache.org/jira/browse/ARROW-1667 Project: Apache Arrow Issue Type: New Feature