[
https://issues.apache.org/jira/browse/BEAM-7274?focusedWorklogId=352877&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-352877
]
ASF GitHub Bot logged work on BEAM-7274:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/19 18:47
Start Date: 03/Dec/19 18:47
Worklog Time Spent: 10m
Work Description: alexvanboxel commented on issue #10247: [BEAM-7274] In
preparation for protocol-buffer schemas, add OneOf and Enumeration logical types
URL: https://github.com/apache/beam/pull/10247#issuecomment-561303499
OK, it took a while... but I've wanted to verify something. I've been
experimenting with how Avro compiles to Java code and how the ordinal value is
created. I just wanted to check out the following scenario:
` { "name": "foo", "type": { "name": "FooEnum", "type": "enum", "symbols":
["x","y"] }},`
we have a schema evolution to:
` { "name": "foo", "type": { "name": "FooEnum", "type": "enum", "symbols":
["a", "x", "y"] }},`
we **upgrade** the pipeline, so the current state is stored. As the ordinal
value is stored in the intermediate state and the schema is evolved by
**pre**-pending a enum value, that means the ordinal values changed (as it's
sequential as defined in the source file: from `x=0 , y=1` > `a=0, x=1, y=2` ).
I do notice the same holds through to the Java Enum type. Not to **Proto**
as it has an explicit number value assigned to an Enum string.
_I don't know if it's an issue... but I wanted to raise it so you're aware
of the side effect_. Is a pipeline even upgradable when the schema changes?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 352877)
Time Spent: 14h 10m (was: 14h)
> Protobuf Beam Schema support
> ----------------------------
>
> Key: BEAM-7274
> URL: https://issues.apache.org/jira/browse/BEAM-7274
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Alex Van Boxel
> Assignee: Alex Van Boxel
> Priority: Minor
> Time Spent: 14h 10m
> Remaining Estimate: 0h
>
> Add support for the new Beam Schema to the Protobuf extension.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
