crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CRUNCH-397) Enrich Scrunch's PCollection and Pipeline traits to match Java API
Date Fri, 16 May 2014 11:19:39 GMT

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

Josh Wills updated CRUNCH-397:
------------------------------

    Attachment: CRUNCH-397.patch

The changes to improve the control over PTypes on Scrunch's PCollection/PTable/PGroupedTable.

Note that the implicit PType creation will now depend on the PTypeFamily of the parent PCollection;
this means that I had to edit two of the integration tests that assumed everything was in
Avro to be explicit about using Avro as a source for text data.

> 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
>         Attachments: CRUNCH-397.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)

Mime
View raw message