You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jozef Vilcek (JIRA)" <ji...@apache.org> on 2018/08/21 13:35:00 UTC
[jira] [Issue Comment Deleted] (BEAM-5180) Broken FileResultCoder
via parseSchema change
[ https://issues.apache.org/jira/browse/BEAM-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jozef Vilcek updated BEAM-5180:
-------------------------------
Comment: was deleted
(was: Submitted a pull request for BEAM-2277 which should fix the root cause and keep the scheme parsing more strict as it is.)
> 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
> Priority: Blocker
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)