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/10/24 17:25:01 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=17433462#comment-17433462 ] 

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

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: P2
>              Labels: stale-P2
>          Time Spent: 2h 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.3.4#803005)