[jira] [Commented] (ARROW-6255) [Rust] [Parquet] Cannot use any published parquet crate due to parquet-format breaking change

["Neville Dipale (JIRA)" <ji...@apache.org>]

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

Neville Dipale commented on ARROW-6255:
---------------------------------------

Hi [~andygrove] [~csun], would yanking 2.6.0 help in the interim?

> [Rust] [Parquet] Cannot use any published parquet crate due to parquet-format breaking change
> ---------------------------------------------------------------------------------------------
>
>                 Key: ARROW-6255
>                 URL: https://issues.apache.org/jira/browse/ARROW-6255
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Rust
>    Affects Versions: 0.12.0, 0.12.1, 0.13.0, 0.14.0, 0.14.1
>            Reporter: Andy Grove
>            Priority: Major
>             Fix For: 0.15.0
>
>
> As a user who wants to use the Rust version of Arrow, I am unable to use any of the previously published versions due to the recent breaking change in parquet-format 2.5.0.
> To reproduce, simply create an empty Rust project using "cargo init example --bin", add a dependency on "parquet-0.14.1" and attempt to build the project.
> {code:java}
>    Compiling parquet v0.13.0
> error[E0599]: no variant or associated item named `BOOLEAN` found for type `parquet_format::parquet_format::Type` in the current scope
>    --> /Users/agrove/.cargo/registry/src/github.com-1ecc6299db9ec823/parquet-0.13.0/src/basic.rs:408:28
>     |
> 408 |             parquet::Type::BOOLEAN => Type::BOOLEAN,
>     |                            ^^^^^^^ variant or associated item not found in `parquet_format::parquet_format::Type`{code}
> This bug has already been fixed in master, but there is no usable published crate. We could consider publishing a 0.14.2 to resolve this or just wait until the 0.15.0 release. We could also consider using this Jira to at least document a workaround, if one exists (maybe Cargo provides a mechanism for overriding transitive dependencies?).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)