[jira] [Updated] (BEAM-10292) DefaultFilenamePolicy.ParamsCoder loses information whether Params's resource ID is file/directory

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-10292:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> 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
>              Labels: Done
>             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)