Hi Jacques,
The paragraph you wrote doesn't quite address my concern about system
compatibility.Would the following paragraph be acceptable? If it
isn't could you expand on your concerns with it?
"Existing Arrow implementations are focused on exposing and operating
between systems running on
IIRC Apex wanted to commit via Gerrit. That was a non-starter. Commits have to
be made by a committer.
Julian
> On Apr 24, 2016, at 3:07 PM, Wes McKinney wrote:
>
> Sending all Gerrit review activity to the mailing list seems adequate to me.
> I don't see how this is especially different from
Sending all Gerrit review activity to the mailing list seems adequate to me.
I don't see how this is especially different from reviewing code on a
website owned by GitHub. I remain hopeful that ASF Infra will set up an
ASF-managed Gerrit.
On Sunday, April 24, 2016, Ted Dunning wrote:
> Just for
Just for the record, Apex had some issues getting Gerrit reviews reflected
in a coherent fashion into the Apache record. I presume that you guys will
have that handled or will check with the Apex devs to learn their
resolution.
On Sun, Apr 24, 2016 at 5:30 PM, Wes McKinney wrote:
> Todd, woul
[
https://issues.apache.org/jira/browse/ARROW-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255663#comment-15255663
]
Uwe L. Korn commented on ARROW-92:
--
PR: https://github.com/apache/arrow/pull/68
> C++: Arr
[
https://issues.apache.org/jira/browse/ARROW-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255664#comment-15255664
]
Uwe L. Korn commented on ARROW-92:
--
To make the actual schema conversion complete, we proba
Todd, would you (or someone who is familiar with Gerrit
administration) mind setting up gerrit.cloudera.org projects that we
can use for apache/arrow and apache/parquet-cpp? We're having more
larger patches to both projects and I'm having a difficult time
staying organized in my reviews on GitHub (
