[
https://issues.apache.org/jira/browse/BEAM-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314314#comment-17314314
]
Brian Rodriguez commented on BEAM-7508:
---------------------------------------
Any context on why it was removed/how we can restore it? <K, <K, V>> is only
practical until you have millions of records to process, with duplicate values
everywhere...
> Expose the current key to the CombineFn
> ---------------------------------------
>
> Key: BEAM-7508
> URL: https://issues.apache.org/jira/browse/BEAM-7508
> Project: Beam
> Issue Type: Improvement
> Components: sdk-ideas, sdk-java-core
> Reporter: Luke Cwik
> Priority: P3
> Labels: Clarified
>
> One can not currently access the key during combining. Having access to the
> key can be useful during various phases.
> There is a less then ideal workaround where the user embeds the key within
> the value turning the combiner over *<K, V>* into a combiner over *<K, <K,
> V>>*.
>
> Originally asked in
> [https://stackoverflow.com/questions/56451796/how-can-i-access-the-key-in-subclass-of-combinerfn-when-combining-a-pcollection]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
