[jira] [Updated] (ARROW-7844) [R] array_to_vector is not thread safe

2020-02-14 Thread Francois Saint-Jacques (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francois Saint-Jacques updated ARROW-7844:
--
Fix Version/s: 0.16.1

> [R] array_to_vector is not thread safe
> --
>
> Key: ARROW-7844
> URL: https://issues.apache.org/jira/browse/ARROW-7844
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: R
>Reporter: Neal Richardson
>Assignee: Francois Saint-Jacques
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0, 0.16.1
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> See 
> [https://travis-ci.org/ursa-labs/arrow-r-nightly/jobs/649649349#L373-L375] 
> for an example on public CI. I was seeing this locally this week but figured 
> I'd screwed up my env somehow.
> {code}
> ── 1. Failure: Lists are preserved when writing/reading from Parquet 
> (@test-parq
>   `object` not equivalent to `expected`.
>   Component "num": Component 1: target is numeric, current is character
> {code}
> It's not always the same column in the data.frame that is affected. Also 
> strange that it's only one column. You'd think that if it were transposing 
> the order somehow, you'd get two that were swapped.
> The test itself is straightforward 
> (https://github.com/apache/arrow/blob/master/r/tests/testthat/test-parquet.R#L124-L137)
>  so this is somewhat troubling.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-7844) [R] array_to_vector is not thread safe

2020-02-13 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-7844:
--
Labels: pull-request-available  (was: )

> [R] array_to_vector is not thread safe
> --
>
> Key: ARROW-7844
> URL: https://issues.apache.org/jira/browse/ARROW-7844
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: R
>Reporter: Neal Richardson
>Assignee: Francois Saint-Jacques
>Priority: Major
>  Labels: pull-request-available
>
> See 
> [https://travis-ci.org/ursa-labs/arrow-r-nightly/jobs/649649349#L373-L375] 
> for an example on public CI. I was seeing this locally this week but figured 
> I'd screwed up my env somehow.
> {code}
> ── 1. Failure: Lists are preserved when writing/reading from Parquet 
> (@test-parq
>   `object` not equivalent to `expected`.
>   Component "num": Component 1: target is numeric, current is character
> {code}
> It's not always the same column in the data.frame that is affected. Also 
> strange that it's only one column. You'd think that if it were transposing 
> the order somehow, you'd get two that were swapped.
> The test itself is straightforward 
> (https://github.com/apache/arrow/blob/master/r/tests/testthat/test-parquet.R#L124-L137)
>  so this is somewhat troubling.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ARROW-7844) [R] array_to_vector is not thread safe

2020-02-13 Thread Francois Saint-Jacques (Jira)


 [ 
https://issues.apache.org/jira/browse/ARROW-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francois Saint-Jacques updated ARROW-7844:
--
Summary: [R] array_to_vector is not thread safe  (was: [R] Parquet list 
column test is flaky)

> [R] array_to_vector is not thread safe
> --
>
> Key: ARROW-7844
> URL: https://issues.apache.org/jira/browse/ARROW-7844
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: R
>Reporter: Neal Richardson
>Assignee: Francois Saint-Jacques
>Priority: Major
>
> See 
> [https://travis-ci.org/ursa-labs/arrow-r-nightly/jobs/649649349#L373-L375] 
> for an example on public CI. I was seeing this locally this week but figured 
> I'd screwed up my env somehow.
> {code}
> ── 1. Failure: Lists are preserved when writing/reading from Parquet 
> (@test-parq
>   `object` not equivalent to `expected`.
>   Component "num": Component 1: target is numeric, current is character
> {code}
> It's not always the same column in the data.frame that is affected. Also 
> strange that it's only one column. You'd think that if it were transposing 
> the order somehow, you'd get two that were swapped.
> The test itself is straightforward 
> (https://github.com/apache/arrow/blob/master/r/tests/testthat/test-parquet.R#L124-L137)
>  so this is somewhat troubling.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)