[jira] [Resolved] (ARROW-11) Mirror JIRA activity to dev@arrow.apache.org

[ https://issues.apache.org/jira/browse/ARROW-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney resolved ARROW-11. --- Resolution: Done Resolved by INFRA-11370 > Mirror JIRA activity to dev@arrow.apache.org > -

[jira] [Commented] (ARROW-23) C++: Add logical "Column" container for chunked data

[ https://issues.apache.org/jira/browse/ARROW-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179232#comment-15179232 ] Wes McKinney commented on ARROW-23: --- See patch https://github.com/apache/arrow/pull/15 >

[jira] [Assigned] (ARROW-23) C++: Add logical "Column" container for chunked data

[ https://issues.apache.org/jira/browse/ARROW-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney reassigned ARROW-23: - Assignee: Wes McKinney > C++: Add logical "Column" container for chunked data > ---

[jira] [Resolved] (ARROW-26) C++: Add developer instructions for building parquet-cpp integration

[ https://issues.apache.org/jira/browse/ARROW-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney resolved ARROW-26. --- Resolution: Fixed Resolved by https://github.com/apache/arrow/pull/12 > C++: Add developer instructions

[jira] [Resolved] (ARROW-10) Fix mismatch of javadoc names and method parameters

[ https://issues.apache.org/jira/browse/ARROW-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney resolved ARROW-10. --- Resolution: Fixed Issue resolved by pull request 3 [https://github.com/apache/arrow/pull/3] > Fix misma

[jira] [Resolved] (ARROW-15) Fix a naming typo for memory.AllocationManager.AllocationOutcome

[ https://issues.apache.org/jira/browse/ARROW-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney resolved ARROW-15. --- Resolution: Fixed Issue resolved by pull request 4 [https://github.com/apache/arrow/pull/4] > Fix a nam

Re: Code reviews / commit-then-review?

It's not like you are going to break an existing release. On Thu, Mar 3, 2016 at 3:11 PM, Julien Le Dem wrote: > sounds good. > > On Thu, Mar 3, 2016 at 1:17 PM, Jason Altekruse > wrote: > > > +1 > > > > On Thu, Mar 3, 2016 at 12:58 PM, Jacques Nadeau > > wrote: > > > > > +1. Sounds good to

[jira] [Resolved] (ARROW-21) C++: Add in-memory schema metadata container

[ https://issues.apache.org/jira/browse/ARROW-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney resolved ARROW-21. --- Resolution: Fixed Issue resolved by pull request 10 [https://github.com/apache/arrow/pull/10] > C++: Ad

Re: Format: storing null count + required/non-nullable types

Returning to this discussion. I did some C++ prototyping https://github.com/apache/arrow/pull/9 https://github.com/apache/arrow/pull/10 A handful of thoughts: 1) It is most useful for compatibility with other systems (e.g. Parquet -- see ARROW-22) to have required/optional in the type metadata,

Re: Code reviews / commit-then-review?

sounds good. On Thu, Mar 3, 2016 at 1:17 PM, Jason Altekruse wrote: > +1 > > On Thu, Mar 3, 2016 at 12:58 PM, Jacques Nadeau > wrote: > > > +1. Sounds good to me. > > > > On Thu, Mar 3, 2016 at 12:35 PM, P. Taylor Goetz > > wrote: > > > > > +1 > > > > > > I think CTR makes sense at this stage.

Re: Code reviews / commit-then-review?

+1 On Thu, Mar 3, 2016 at 12:58 PM, Jacques Nadeau wrote: > +1. Sounds good to me. > > On Thu, Mar 3, 2016 at 12:35 PM, P. Taylor Goetz > wrote: > > > +1 > > > > I think CTR makes sense at this stage. RTC would slow things down > > considerably. > > > > -Taylor > > > > > On Mar 3, 2016, at 3:00

Re: Code reviews / commit-then-review?

+1. Sounds good to me. On Thu, Mar 3, 2016 at 12:35 PM, P. Taylor Goetz wrote: > +1 > > I think CTR makes sense at this stage. RTC would slow things down > considerably. > > -Taylor > > > On Mar 3, 2016, at 3:00 PM, Julian Hyde wrote: > > > > +1 > > > > Thanks for asking. > > > > > >> On Mar 3,

Re: Code reviews / commit-then-review?

+1 I think CTR makes sense at this stage. RTC would slow things down considerably. -Taylor > On Mar 3, 2016, at 3:00 PM, Julian Hyde wrote: > > +1 > > Thanks for asking. > > >> On Mar 3, 2016, at 11:22 AM, Wes McKinney wrote: >> >> hi folks, >> >> I'm going to have many C++ and Python pa

Re: Code reviews / commit-then-review?

+1 Thanks for asking. > On Mar 3, 2016, at 11:22 AM, Wes McKinney wrote: > > hi folks, > > I'm going to have many C++ and Python patches the next few weeks, any > objections to proceeding in commit-then-review mode (particularly on the > Python side) for the time being in the interest of expe

Re: Arrow examples

Serializing Spark DataFrame in either Java or Scala would suffice for the use case, but there may be follow-on JIRAs to make the Arrow adapters more accessible. pandas only needs access to flat schemas for now, for example, so nested Spark SQL schemas could be handled in follow-up work. Note: this

Code reviews / commit-then-review?

hi folks, I'm going to have many C++ and Python patches the next few weeks, any objections to proceeding in commit-then-review mode (particularly on the Python side) for the time being in the interest of expediency? I will be more than happy to collect feedback from merged patches into new JIRAs a

Re: Arrow examples

Hi Wes, Thanks for raising the ticket. So it seems like Spark 2.0 will not have support for Arrow. Also does SPARK-13534 cover Arrow serialization for Spark's JAVA API, or do we need to raise a separate ticket for that? As of now, I only have a high-level understanding of Arrow and it's data stru