Hi Bryan,
Thanks for your comment.
OK. I move https://issues.apache.org/jira/browse/ARROW-5764
to 1.0.0 from 0.14.0.
Thanks,
--
kou
In
"Re: 0.14.0: Javadoc failed with OpenJDK 11" on Fri, 28 Jun 2019 14:26:13
-0700,
Bryan Cutler wrote:
> I agree with Wes that JDK8 is still the main
Sutou Kouhei created ARROW-5793:
---
Summary: [Release] Avoid duplicate known host SSH error in
dev/release/03-binary.sh
Key: ARROW-5793
URL: https://issues.apache.org/jira/browse/ARROW-5793
Project:
Renjie Liu created ARROW-5792:
-
Summary: [Rust] [Parquet] A visitor trait for parquet types.
Key: ARROW-5792
URL: https://issues.apache.org/jira/browse/ARROW-5792
Project: Apache Arrow
Issue
Sutou Kouhei writes:
> How about creating a mirror repository on
> https://gitlab.com/ only to run CI jobs?
>
> This is an idea that is described in
> https://issues.apache.org/jira/browse/ARROW-5673 .
>
> GitLab CI can attach external workers. So we can increase CI
> capacity by adding our new
Hey,
I was thinking more about using GitHub actions in the same way as Kou is
proposing to use GitLab CI. So basically to orchestrate CI workload on our
workers. Sorry for not specifying.
GitLab is currently more mature but on the other hand we're already on
GitHub. We should probably evaluate
Bogdan Klichuk created ARROW-5791:
-
Summary: pyarrow.csv.read_csv hangs + eats all RAM
Key: ARROW-5791
URL: https://issues.apache.org/jira/browse/ARROW-5791
Project: Apache Arrow
Issue Type:
Hi,
How about creating a mirror repository on
https://gitlab.com/ only to run CI jobs?
This is an idea that is described in
https://issues.apache.org/jira/browse/ARROW-5673 .
GitLab CI can attach external workers. So we can increase CI
capacity by adding our new workers. GitLab also provides
hey Jacques,
I think in the case of dictionary encoding, any algorithm should be
operating with the dictionary for a particular field in a record batch
already in hand. Certain algorithms optimized for dictionary-encoded
data (like hash aggregations) may have to branch at fragment merge
steps
hi Rok,
I would guess that GitHub Actions will have the same resource and
hardware limitations that Travis CI and Appveyor currently have, as
well as organization-level resource contention with the rest of the
ASF.
We need to have dedicated, powerful hardware (more cores, more RAM),
with more
Brock Mendel created ARROW-5790:
---
Summary: Passing zero-dim numpy array to pa.array causes segfault
Key: ARROW-5790
URL: https://issues.apache.org/jira/browse/ARROW-5790
Project: Apache Arrow
Micah Kornfield created ARROW-5789:
--
Summary: [C++] Small Warning/Linkage cleanups
Key: ARROW-5789
URL: https://issues.apache.org/jira/browse/ARROW-5789
Project: Apache Arrow
Issue Type:
GitHub Actions are currently in limited public beta and appear to be
similar to GitLab CI: https://github.com/features/actions
More here: https://help.github.com/en/articles/about-github-actions
Rok
On Fri, Jun 28, 2019 at 7:06 PM Wes McKinney wrote:
> Based on the discussion in
>
Sutou Kouhei created ARROW-5788:
---
Summary: [Rust] Use { version = "...", path = "../..." } for arrow
and parquet dependencies
Key: ARROW-5788
URL: https://issues.apache.org/jira/browse/ARROW-5788
Sutou Kouhei created ARROW-5787:
---
Summary: [Release][Rust] Use local modules to verify RC
Key: ARROW-5787
URL: https://issues.apache.org/jira/browse/ARROW-5787
Project: Apache Arrow
Issue
14 matches
Mail list logo