You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/03 16:42:00 UTC
[jira] (BEAM-72) Source design pattern: option to retain metadata
[ https://issues.apache.org/jira/browse/BEAM-72 ]
Danny McCormick deleted comment on BEAM-72:
-------------------------------------
was (Author: JIRAUSER282469):
This isn't actually real, but this issue has been migrated to https://github.com/apache/beam/issues/17847
> Source design pattern: option to retain metadata
> ------------------------------------------------
>
> Key: BEAM-72
> URL: https://issues.apache.org/jira/browse/BEAM-72
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-core
> Reporter: Dan Halperin
> Priority: P3
> Labels: Clarified
>
> * FileBasedSource: user may want to know original path, directory, line number, byte offset, etc.
> * PubSubIO: user may want to know things about the originating message (such as metadata attributes), not just they payload. BEAM-53
> * etc.
> We should have a standard pattern for this that provides a good guideline for implementing sources.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)