[
https://issues.apache.org/jira/browse/BEAM-9360?focusedWorklogId=397505&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-397505
]
ASF GitHub Bot logged work on BEAM-9360:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Mar/20 11:28
Start Date: 04/Mar/20 11:28
Worklog Time Spent: 10m
Work Description: JozoVilcek commented on issue #10943: [BEAM-9360] Fix
equivalence check for FieldType
URL: https://github.com/apache/beam/pull/10943#issuecomment-594467858
@alexvanboxel problem is not with proto extensions. Proto extension just did
uncover the bug because it uses filed metadata.
What kind of test do you have in mind to put there?
----------------------------------------------------------------
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: 397505)
Time Spent: 20m (was: 10m)
> Schema FieldType should not consider metadata for equivalence
> -------------------------------------------------------------
>
> Key: BEAM-9360
> URL: https://issues.apache.org/jira/browse/BEAM-9360
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Affects Versions: 2.19.0
> Reporter: Jozef Vilcek
> Assignee: Jozef Vilcek
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> FieldType `equivalent()` check should not require exact match in fields
> metadata.
> Discussion in dev mailing list:
> [https://lists.apache.org/[email protected]:lte=1M:Schema%20Convert%20transform%20fails%20on%20type%20metadata]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
