Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-12911

Errors hydrating beam:coder:row:v1 should indicate the problematic field

Details

    • Improvement
    • Status: Resolved
    • P3
    • Resolution: Fixed
    • None
    • 2.34.0
    • sdk-java-core, sdk-py-core
    • None

    Description

      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:

      ValueError: No logical type registered for URN 'beam:logical_type:javasdk:v1'
      

      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.

      Attachments

        Issue Links

          Activity

            People

              bhulette Brian Hulette
              bhulette Brian Hulette
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h 20m
                  4h 20m