You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:04 UTC
[jira] [Updated] (BEAM-1194) DataflowRunner should canonicalize gcpTempLocation/stagingLocation/etc formats.
[ https://issues.apache.org/jira/browse/BEAM-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-1194:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> DataflowRunner should canonicalize gcpTempLocation/stagingLocation/etc formats.
> -------------------------------------------------------------------------------
>
> Key: BEAM-1194
> URL: https://issues.apache.org/jira/browse/BEAM-1194
> Project: Beam
> Issue Type: Test
> Components: runner-dataflow
> Reporter: Dan Halperin
> Priority: P3
> Labels: newbie, starter
>
> Cloud Dataflow has a minor history of small bugs related to various code paths expecting there to be or not be a trailing forward-slash in these location fields. The way that Beam's integration tests are set up, we are likely to only have one of these two cases tested (there is a single set of integration test pipeline options).
> We should add a dedicated DataflowRunner integration test to handle this case.
> Actually, we should probably canonicalize the URLs so that we only ever produce one version.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)