[
https://issues.apache.org/jira/browse/CRUNCH-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661822#comment-13661822
]
Gabriel Reid commented on CRUNCH-208:
-------------------------------------
+1. That's definitely a pattern that seems to come up very regularly.
I guess that's what o.a.c.fn.MapValues is intended for, but I never end up
using it because feels wrong to extend from MapValuesFn instead of just from
MapFn. What I usually end up doing is using a MapValuesFn that wraps a MapFn to
get this same functionality, but with the addition of this method maybe we
could even deprecate MapValuesFn.
> Add a mapValues convenience function to PTable and PGroupedTable
> ----------------------------------------------------------------
>
> Key: CRUNCH-208
> URL: https://issues.apache.org/jira/browse/CRUNCH-208
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-208.patch
>
>
> Working on Cloudera ML, I find myself writing lots of functions where I'm
> only modifying the values of a PTable or PGroupedTable and just passing along
> the keys as they are, so I wrote some functions to help me implement that
> pattern more easily.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
