You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2014/05/20 06:07:38 UTC

[jira] [Resolved] (CRUNCH-397) Enrich Scrunch's PCollection and Pipeline traits to match Java API

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

Josh Wills resolved CRUNCH-397.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8.3
                   0.10.0

Pushed to master and 0.8.

> Enrich Scrunch's PCollection and Pipeline traits to match Java API
> ------------------------------------------------------------------
>
>                 Key: CRUNCH-397
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-397
>             Project: Crunch
>          Issue Type: Bug
>          Components: Scrunch
>            Reporter: Josh Wills
>             Fix For: 0.10.0, 0.8.3
>
>         Attachments: CRUNCH-397.patch, CRUNCH-397b.patch, CRUNCH-397c.patch
>
>
> We've added a ton of stuff to the Java APIs over the last couple of releases, and I'd like to add as much of it as I can to the Scrunch APIs. At the very least, I'd like to be sure that the client has fine-grained control over the PTypes that are being used with each PCollection that gets created, no matter what mechanism is used to do it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)