OK, I will publish to reserve the name.
I think we will see very rapid development over the coming weeks as we
flesh this out. I also believe we have quite a few people waiting in the
wings who will start contributing as well. It could make sense to have a
separate release cycle at least initially
hi Andy,
I think it's fine for you to claim the "arrow" or "apache-arrow" real
estate on crates.io so no one else does, we just can't call it a
"release" unless the artifact (or the source tarball that generates
it) goes through the ASF release process.
For Rust, we'll need to decide whether to r
Assuming the Rust Arrow PR is merged, we will want to start publishing
releases to crates.io at some point. In fact, we should publish the 0.1.0
sooner rather than later to reserve the name "arrow" as crates.io operates
on a first-come first-served basis.
For those not familiar with the Rust ecosy
Hi,
Can I get an invite as well?
Thank you.
Alex
On 03/28/2018 09:28 PM, Aneesh Karve wrote:
Hi Wes, please add me to the Gcal invite. Thank you.
ᐧ
Hi Wes, please add me to the Gcal invite. Thank you.
ᐧ
> As far as Bazel goes, I can put up a patch and discuss some of the pros/cons
> in the context of stated issues around packaging. It likely won't help with
> the release reliability questions, which seem separate.
Indeed, the issues we have had with packaging are not (AFAICT) related
to the bui
oh gosh, I just saw this reply too!
I've just caught up with the thread around the build+release/packaging. As
far as Bazel goes, I can put up a patch and discuss some of the pros/cons
in the context of stated issues around packaging. It likely won't help with
the release reliability questions, wh
+1
Great move.
Your presence looms large over this project, so stepping back will give others
the chance to take the lead.
I know (from other projects) how oppressive it is to be the main “go to” person
in a project. It irks me, for instance, when people address comments in PRs
directly to me
hi folks,
It's been quite a lot of work the last few years building the Apache
Arrow project and community until this point. I began working on some
flavor of an Arrow-like project in early 2015, later merging with the
efforts of folks from Apache {Drill, Calcite, Kudu, Impala, Spark,
...} and oth
Antoine Pitrou created ARROW-2362:
-
Summary: [Python] Decimal conversions are slow
Key: ARROW-2362
URL: https://issues.apache.org/jira/browse/ARROW-2362
Project: Apache Arrow
Issue Type: Wish
Krisztian and I have been working together on a native Rust implementation
of Arrow and have been exploring some different approaches.
I thought it was probably time to update everyone on this mailing list and
open this up to some more opinions.
I have filed a JIRA (https://issues.apache.org/jira
Andy Grove created ARROW-2361:
-
Summary: Native Rust Implementation
Key: ARROW-2361
URL: https://issues.apache.org/jira/browse/ARROW-2361
Project: Apache Arrow
Issue Type: New Feature
C
Xianjin YE created ARROW-2360:
-
Summary: Add set_chunksize for RecordBatchReader in
arrow/record_batch.h
Key: ARROW-2360
URL: https://issues.apache.org/jira/browse/ARROW-2360
Project: Apache Arrow
13 matches
Mail list logo
