Jozef Vilcek created BEAM-5180:
----------------------------------
Summary: Broken FileResultCoder via parseSchema change
Key: BEAM-5180
URL: https://issues.apache.org/jira/browse/BEAM-5180
Project: Beam
Issue Type: Bug
Components: sdk-java-core
Affects Versions: 2.6.0
Reporter: Jozef Vilcek
Assignee: Kenneth Knowles
Recently this commit introduced more strict schema parsing which is breaking
the contract between `FileResultCoder` and `FileSystems.matchNewResource()`.
Coder takes `ResourceId` and serialize it via `toString` methods and then
relies on filesystem being able to parse it back again. Having strict
`scheme://` breaks this at least for `Hadoop` filesystem which use `URI for
`ResourceId` and produce `toString()` in form of `hdfs:/some/path`
I guess the `ResourceIdCoder` is suffering the same problem.
Either scheme parsing should be less strict or `ResourceId.toString()` for
`hadoop` fixed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
