You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/10/25 22:17:00 UTC
[jira] [Commented] (BEAM-12883) FileSystems ReadableFileCoder
should support Metadata#lastModifiedMillis()
[ https://issues.apache.org/jira/browse/BEAM-12883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434000#comment-17434000 ]
Kenneth Knowles commented on BEAM-12883:
----------------------------------------
Is this now resolved?
> FileSystems ReadableFileCoder should support Metadata#lastModifiedMillis()
> --------------------------------------------------------------------------
>
> Key: BEAM-12883
> URL: https://issues.apache.org/jira/browse/BEAM-12883
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Brachi Packter
> Assignee: Brachi Packter
> Priority: P3
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Currently, there is a separated coder for Metadata which cares about `Metadata#lastModifiedMillis()`.
> The issue is that the `ReadableFileCoder` always uses the default `Metadata` coder.
> We need to create a similar coder for `ReadableFileCoder`: ``ReadableFileCoderV2` which just use the corresponding `MetadataCoderV2`.
> Without doing so `lastModifiedMillis` will remain zero.
> There is also no way to create custom coder in our side since `FileIO.ReadableFile` has no public method to initiate new instance of it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)