You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/11/07 17:26: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=17440058#comment-17440058 ]
Beam JIRA Bot commented on BEAM-12795:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> 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: 3h
> 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.1#820001)