You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Neville Dipale (Jira)" <ji...@apache.org> on 2020/11/28 12:40:00 UTC

[jira] [Commented] (ARROW-4170) [CI/Rust] Create separate CI job for parquet crate

    [ https://issues.apache.org/jira/browse/ARROW-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239950#comment-17239950 ] 

Neville Dipale commented on ARROW-4170:
---------------------------------------

With parquet now depending on arrow, and datafusion depending on parquet, I'm closing this.

> [CI/Rust] Create separate CI job for parquet crate
> --------------------------------------------------
>
>                 Key: ARROW-4170
>                 URL: https://issues.apache.org/jira/browse/ARROW-4170
>             Project: Apache Arrow
>          Issue Type: Test
>          Components: Rust
>            Reporter: Chao Sun
>            Priority: Major
>
> Now since Rust parquet implementation is moved into a separate crate, it's better to create a separate CI job that should be triggered whenever there's code change for it. On the other hand, changes go to arrow crate should only trigger the CI job against arrow.



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