[jira] [Commented] (BEAM-12883) FileSystems ReadableFileCoder should support Metadata#lastModifiedMillis()

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-12883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472914#comment-17472914 ] 

Beam JIRA Bot commented on BEAM-12883:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>              Labels: stale-assigned
>          Time Spent: 4h 50m
>  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.20.1#820001)