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

Filesystems.matchSingleFileSpec throws away the actual failure exception

Details

    Description

      At [1] the result of a non-OK match causes an exception to be thrown. But the exception does not include the actual cause of the failure, so it cannot be efficiently debugged. It appears that the design of MatchResult is that it should call metadata() without bothering to check status, so that the underlying exception can be re-raised and caught and put in the chain of causes, as it should be.

      [1] https://github.com/apache/beam/blob/c2f0d282337f3ae0196a7717712396a5a41fdde1/sdks/java/core/src/main/java/org/apache/beam/sdk/io/FileSystems.java#L190

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kenn Kenneth Knowles
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

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