[jira] [Work logged] (BEAM-12911) Errors hydrating beam:coder:row:v1 should indicate the problematic field

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-12911?focusedWorklogId=653159&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-653159 ]

ASF GitHub Bot logged work on BEAM-12911:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Sep/21 19:33
            Start Date: 20/Sep/21 19:33
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #15538:
URL: https://github.com/apache/beam/pull/15538#issuecomment-923228676


   Oops I referenced the wrong jira in multiple places. The correct jira is BEMA-12911


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 653159)
    Remaining Estimate: 0h
            Time Spent: 10m

> Errors hydrating beam:coder:row:v1 should indicate the problematic field
> ------------------------------------------------------------------------
>
>                 Key: BEAM-12911
>                 URL: https://issues.apache.org/jira/browse/BEAM-12911
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core, sdk-py-core
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When creating beam:coder:row:v1 instances, both the Java SDK and Python SDK can fall back to use Python- or Java- native coders (e.g. beam:logical:javasdk:v1). This can be problematic in multi-language pipelines, where these types are almost never understood by the other SDK(s).
> This leads to obtuse, non-actionable error messages, like:
> {code}
> ValueError: No logical type registered for URN 'beam:logical_type:javasdk:v1'
> {code}
> We should modify coder hydration logic in both Java and Python to identify the field that has an issue, so the user may have a change to understand and resolve it.



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