You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2020/08/20 17:03:00 UTC
[jira] [Updated] (BEAM-10292) DefaultFilenamePolicy.ParamsCoder
loses information whether Params's resource ID is file/directory
[ https://issues.apache.org/jira/browse/BEAM-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik updated BEAM-10292:
-----------------------------
Fix Version/s: 2.25.0
> DefaultFilenamePolicy.ParamsCoder loses information whether Params's resource ID is file/directory
> --------------------------------------------------------------------------------------------------
>
> Key: BEAM-10292
> URL: https://issues.apache.org/jira/browse/BEAM-10292
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: David Janicek
> Assignee: David Janicek
> Priority: P2
> Fix For: 2.25.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> *DefaultFilenamePolicy.ParamsCoder* uses simple *StringUtf8Coder* for encoding/decoding *DefaultFilenamePolicy.Params*'s *baseFilename* and therefore looses information whether *Params.baseFilename* resource ID is file or directory.
> The result is that it's effectively preventing user to define directory as *baseFilename provider* when using dynamic destinations because after deserialization it's translated to file.
> Solution is easy - use *ResourceIdCoder* for encoding/decoding.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)