[
https://issues.apache.org/jira/browse/BEAM-13640?focusedWorklogId=766713&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-766713
]
ASF GitHub Bot logged work on BEAM-13640:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/May/22 15:04
Start Date: 05/May/22 15:04
Worklog Time Spent: 10m
Work Description: aaltay commented on PR #15699:
URL: https://github.com/apache/beam/pull/15699#issuecomment-1118667789
What is the next step on this PR?
Issue Time Tracking
-------------------
Worklog Id: (was: 766713)
Time Spent: 3h 20m (was: 3h 10m)
> Add MetadataDynamicCoder to support encode-decode for new fields in Metatdata
> -----------------------------------------------------------------------------
>
> Key: BEAM-13640
> URL: https://issues.apache.org/jira/browse/BEAM-13640
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Brachi Packter
> Priority: P3
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> This Issue is to solve similar problems to wha I had in
> [BEAM-12883.|https://issues.apache.org/jira/browse/BEAM-12883?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel]
> Currently there are 2 Coders for Metadata: default one:
> org.apache.beam.sdk.io.fs.MetadataCoder and enhanced one
> org.apache.beam.sdk.io.fs.MetadataCoderV2, the last can also decode-encode
> lastModifiedMillis and it is done in a new coder in order to support backward
> compatibility.
> This will be hard to maintain, we will need to create a new coder for any new
> field that will be added to Metadata.
> So, as suggested in this [comment:
> #15510|https://github.com/apache/beam/pull/15510#issuecomment-928390587], we
> need to have some new generic coder : MetadataDynamicCoder.
> MetadataDynamicCoder can decode/encode any new fields added to Metadata by
> sending getter, setter and coder.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
