[BEAM-5180] Broken FileResultCoder via parseSchema change

• Type: Bug
• Status: Resolved
• Priority: P0
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.7.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Ankur Goenka
• Reporter: Jozef Vilcek
• Created: 20/Aug/18 12:08
• Updated: 06/Oct/20 21:51
• Resolved: 24/Aug/18 20:59

Description

Recently this commit

https://github.com/apache/beam/commit/3fff58c21f94415f3397e185377e36d3df662384

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.

Issue Links

• links to: GitHub Pull Request #6251