[jira] [Created] (ARROW-3850) Support MapType and StructType for PySpark integration

Florian Wilhelm created ARROW-3850: -- Summary: Support MapType and StructType for PySpark integration Key: ARROW-3850 URL: https://issues.apache.org/jira/browse/ARROW-3850 Project: Apache Arrow

[jira] [Created] (ARROW-3849) Leverage Armv8 crc32 extension instructions to accelerate the hash computation for Arm64.

Yuqi Gu created ARROW-3849: -- Summary: Leverage Armv8 crc32 extension instructions to accelerate the hash computation for Arm64. Key: ARROW-3849 URL: https://issues.apache.org/jira/browse/ARROW-3849 Project:

Re: [DISCUSS] Rust add adapter for parquet

> Is the change to the nightly compiler the kind of thing that the PMC should > vote on? A vote is not necessary if there is reasonable consensus. On Wed, Nov 21, 2018 at 9:11 PM paddy horan wrote: > > I was using x86_64-pc-windows-msvc but it was just a quick test, I’ll take a > closer look

Re: [DISCUSS] Rust add adapter for parquet

I was using x86_64-pc-windows-msvc but it was just a quick test, I’ll take a closer look when I get a chance. I agree that lack of support for 32 bit should not hold this up. Is the change to the nightly compiler the kind of thing that the PMC should vote on? This could be done in advance of

Re: [DISCUSS] Rust add adapter for parquet

> A bigger issue is windows support for parquet-rs, Chao – I don’t believe that parquet-rs supports windows, right? When I test it myself I get errors regarding clang and libclang which parquet-rs must use. I think there are some issue regarding clang working with zstd on 32-bit platform.

Re: Master build failure (timeout)

Yes, that one has been timing out periodically lately so you can either restart the build or ignore it. On Wed, Nov 21, 2018, 1:38 PM Andy Grove The build triggered by my PR merge failed in the Ruby build. Looks like it > timed out while installing some prerequisites. > > What is the procedure

Master build failure (timeout)

The build triggered by my PR merge failed in the Ruby build. Looks like it timed out while installing some prerequisites. What is the procedure for handling this? Should I just trigger a rebuild in Travis? Thanks, Andy.

RE: [DISCUSS] Rust add adapter for parquet

I think using nightly is fine for the reasons mentioned already. We should switch our CI to still run CI against stable (non fatal) so we know when we can make the move back to stable. A bigger issue is windows support for parquet-rs, Chao – I don’t believe that parquet-rs supports windows,

Re: [DISCUSS] Rust add adapter for parquet

> Can you remind us all why nightly is required? Here's a tracking issue for all the unstable features parquet-rs uses. I'm personally inclined to use nightly since some new features such as specialization makes development much easier. Like Andy

Re: [DISCUSS] Rust add adapter for parquet

The steps from here are for you all to get the codebase into a state that is ready for donation, including ASF license headers, etc. A pull request into apache/arrow would be the best thing Then we have to do the following * Vote on the Arrow mailing list * Receive ICLAs from contributors *

Re: JIRA notifications

Here is a gmail search query that would do this: to:(dev@arrow.apache.org) subject:([jira]) -Rust On Wed, Nov 21, 2018 at 10:34 AM Wes McKinney wrote: > > hey Andy, > > A lot of us use gmail. > > On the mailing list, we have two main kinds of e-mails: > > * Discussions written directly be people

Re: JIRA notifications

hey Andy, A lot of us use gmail. On the mailing list, we have two main kinds of e-mails: * Discussions written directly be people * New issue notifications The new issue notifications have titles like "[jira] [Created] (ARROW-2653) [C++] Refactor hash table support". See

Re: JIRA notifications

I have a somewhat related question. I currently use gmail as my email client and it works OK overall, but it's pretty horrible for following this mailing list. I was curious what email clients others here use. Thanks, Andy. On Wed, Nov 21, 2018 at 3:58 AM Maximilian Michels wrote: > Hi! > >

Re: JIRA notifications

hi On Wed, Nov 21, 2018 at 9:22 AM Maximilian Michels wrote: > > Hi Wes, > > I understand that you want to be up to date with regards to all issues > in Arrow. I think for a lot of people that won't be the case. They'd > rather opt-in in or watch individual issues. Agreed. The hope/intent is

Re: [DISCUSS] Rust add adapter for parquet

Renjie, Can you remind us all why nightly is required? My personal feeling is that stable is a nice-to-have, but Rust is still moving fast and we are on the bleeding edge here so I'm OK with Arrow relying on nightly for now. Maybe we can have a plan to transition back to stable for a future

Re: [DISCUSS] Rust add adapter for parquet

That sounds great. But parquet-rs currently relies on nightly rust, that would be the first problem to resolve. On Wed, Nov 21, 2018 at 4:49 AM Andy Grove wrote: > This sounds like a great idea. > > With support for both CSV and Parquet in the Arrow crate, it would be nice > to design a

Re: JIRA notifications

Hi Wes, I understand that you want to be up to date with regards to all issues in Arrow. I think for a lot of people that won't be the case. They'd rather opt-in in or watch individual issues. However, it looks like there is no other way to get notified of newly created issues; unless

Re: JIRA notifications

Only new issue notifications are being sent to the mailing list. issues@ receives all comments / changes so is at least 10x higher traffic. I get issues@ in my inbox personally because it helps me stay on top of what's going on in all aspects of the project. I think new issues are relevant to

JIRA notifications

Hi! Do you think it would make sense to send JIRA notifications to a separate mailing list? Some people just want to casually follow the mailing list and it requires a filter to delete all the JIRA spam. I see there is already an "issues" mailing list which receives the JIRA notifications:

[jira] [Created] (ARROW-3848) [R] allow nbytes to be missing in Readable$Read()

Romain François created ARROW-3848: -- Summary: [R] allow nbytes to be missing in Readable$Read() Key: ARROW-3848 URL: https://issues.apache.org/jira/browse/ARROW-3848 Project: Apache Arrow