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/04 21:02:00 UTC
[jira] [Commented] (BEAM-12795) KVs should not be needed when using schemas
[ https://issues.apache.org/jira/browse/BEAM-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549474#comment-17549474 ]
Danny McCormick commented on BEAM-12795:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/21067
> KVs should not be needed when using schemas
> -------------------------------------------
>
> Key: BEAM-12795
> URL: https://issues.apache.org/jira/browse/BEAM-12795
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-core
> Reporter: Reuven Lax
> Priority: P3
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> When using schemas there should be no need to require a KV, as any. key or keys can be act as the K or a V in a KV. Users can use schemas without the need for KV in all cases except for state/timers DoFns, which today require that the input have type KV. We would like to eliminate this requirement. Users should be able to specify a key field extraction in their ParDo, e.g.
> ParDo.of(...).withKeyFields("user.location.city"));
> Or in the DoFn itself.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)