[
https://issues.apache.org/jira/browse/BEAM-9502?focusedWorklogId=424390&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-424390
]
ASF GitHub Bot logged work on BEAM-9502:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Apr/20 20:10
Start Date: 17/Apr/20 20:10
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #11447: [BEAM-9502] makes
Schema UUID generation deterministic
URL: https://github.com/apache/beam/pull/11447#issuecomment-615442205
I would like to talk about the use case a bit more. I think this is probably
to do with update support on the Dataflow runner, in which case this may not be
the right solution (and may not be a sufficient change).
----------------------------------------------------------------
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: 424390)
Time Spent: 50m (was: 40m)
> SchemaCoder assigns random UUID, causes Dataflow's compatibility check to fail
> ------------------------------------------------------------------------------
>
> Key: BEAM-9502
> URL: https://issues.apache.org/jira/browse/BEAM-9502
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, sdk-java-core
> Reporter: Yaron Neuman
> Assignee: Cameron Morgan
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> After fe4b7794, _Schema.equals_ comparing only the UUIDs for faster
> comparison.
> After 0b3b18c6 _SchemaCoder_ forcing random UUID when schema.uuid is null.
> thus, when trying to update (--update) a Dataflow job with row schemas in
> user-code, the compatibility check will fail because SchemaCoder produce
> another random UUID.
>
> The user can set the UUID after creating the Schema, but not with
> Schema.Builder
> and I'm afraid most users, that are not aware to the internal
> implementation, won't do that.
>
> In my branch, I added _.withUUID_ and _.withRandomUUID_ to _Schema.Builder_
> But I think a better solution will be to calculate the UUID based on the
> schema itself.
> any thoughts?
> [~reuvenlax]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
