[ https://issues.apache.org/jira/browse/BEAM-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123268#comment-17123268 ]
Beam JIRA Bot commented on BEAM-4734: ------------------------------------- This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3. Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean. > TableRowJsonCoder looses type > ----------------------------- > > Key: BEAM-4734 > URL: https://issues.apache.org/jira/browse/BEAM-4734 > Project: Beam > Issue Type: Bug > Components: io-java-gcp > Reporter: Etienne Chauchot > Priority: P2 > Labels: stale-P2 > > When we create a TableRow (e.g. in a row function in bigQueryIO) using new > TableRow().set(), for ex a long gets boxed into a Long. But when it is > encoded using TableRowJsonCoder and then re-read it might be decoded as an > Integer if the value fits into Integer. It causes failure in asserts in tests > like write then read. > > Link to the discussion in the ML: > https://lists.apache.org/thread.html/727fd63b2aa4890bed5953574a7e01485ef785de4558fd2327136ab8@%3Cdev.beam.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)