I am also interested on this . Do we need to know drill before start
implementing not a for arrow .
On Jun 10, 2016 9:45 PM, "Wail Alkowaileet" wrote:
> On Wed, Jun 8, 2016 at 9:26 PM, Micah Kornfield
> wrote:
>
> > Hi Steven,
> > Is the patch focused
I am not sure how to do this while continuing to use Travis CI. I am
not able to set up a new CI environment (e.g. Jenkins + gerrit a la
Kudu) right now.
I am having a hard time keeping track of the state of code reviews, so
I've proposed this triage solution (which will involve an extra force
[
https://issues.apache.org/jira/browse/ARROW-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-203.
Resolution: Fixed
Issue resolved by pull request 83
[https://github.com/apache/arrow/pull/83]
>
More design work is needed on the metadata specification -- I would
not use either codebase as a reference for doing a different
implementation until the specification / format documents are complete
enough to enable a "clean room" implementation.
I will leave Steven or Jacques from the Drill
Hi Wes,
What is the most complete arrow version at the moment? I can see C++ and Python
are most active and Java was coped from Drill. So does this mean that we can
use the C++ version as a reference?
I also want to help you. I can do metadata read/write, if nobody doing it.
Thanks,
-Kiril
>
On Wed, Jun 8, 2016 at 9:26 PM, Micah Kornfield
wrote:
> Hi Steven,
> Is the patch focused on the alignment/padding. Or are there other
> issues as well?
>
I'm interested on this as well
>
> Thanks,
> Micah
>
> On Tue, Jun 7, 2016 at 11:22 PM, Steven Phillips
Uwe L. Korn created ARROW-215:
-
Summary: C++: Support other integer types in Parquet I/O
Key: ARROW-215
URL: https://issues.apache.org/jira/browse/ARROW-215
Project: Apache Arrow
Issue Type: New
Uwe L. Korn created ARROW-214:
-
Summary: C++: Add String support to Parquet I/O
Key: ARROW-214
URL: https://issues.apache.org/jira/browse/ARROW-214
Project: Apache Arrow
Issue Type: New Feature