thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Dettai (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (THRIFT-5314) Enum forward compatibility
Date Thu, 19 Nov 2020 16:54:00 GMT

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

Remi Dettai edited comment on THRIFT-5314 at 11/19/20, 4:53 PM:
----------------------------------------------------------------

I must admit that I don't understand why Flatbuffer ended up with that design, I just assumed
that if they converged to it after such a long and passionate debate, there must be a reason
:D .

>From a users perspective, I think I prefer your option.


was (Author: rdettai):
I must admit that I don't understand why Flatbuffer ended up with that design, I just assumed
that if they converged to it after such a long and passionate debate, there must be a reason
:D

>From a users perspective, I think I prefer you option.

> Enum forward compatibility
> --------------------------
>
>                 Key: THRIFT-5314
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5314
>             Project: Thrift
>          Issue Type: Bug
>          Components: Rust - Compiler, Rust - Library
>    Affects Versions: 0.13.0
>            Reporter: Remi Dettai
>            Priority: Major
>
> It seems that enums in the Rust implem are not forward compatible. As Thrift enums are
mapped 1:1 to Rust enum, if a newer Thrift definition adds a case to an enum, an error will
be returned when parsing the message.
> Is this intended? Is there a workaround?
> (We met this problem in the Rust parquet implem: https://issues.apache.org/jira/browse/ARROW-10553)



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

Mime
View raw message