[jira] [Updated] (BEAM-12795) KVs should not be needed when using schemas

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-12795:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> 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)