crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-509) Crunch with Spark doesn't name all outputs
Date Wed, 08 Apr 2015 15:07:12 GMT


Josh Wills commented on CRUNCH-509:

[~tomwhite] the outputs in Crunch-on-Spark are not named, as Crunch-on-Spark doesn't use multiple
outputs. Spark only writes one RDD at a time, so I hadn't bothered to name the outputs yet.

[~mkwhitacre] I _think_ that just renaming all of the outputs to be named "out0" should work
in conjunction w/the CrunchOutputFormat, but I don't have time to test it out today. I can
take it out for a spin tomorrow and see if I can get it working. It would be nice to start
laying a foundation for multiple outputs in Spark.

> Crunch with Spark doesn't name all outputs
> ------------------------------------------
>                 Key: CRUNCH-509
>                 URL:
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.11.0
>            Reporter: Micah Whitacre
>            Assignee: Josh Wills
>             Fix For: 0.12.0
> Crunch currently does not "name" all outputs when running with a SparkPipeline.  This
becomes a problem as some Targets (based on CRUNCH-82) have coded in checked to ensure that
the name must be populated.  Specifically the implementation I'm running into issues with
is the Kite DatasetTarget[2].
> Need to read up a bit on context to see if it is a Crunch/Kite issue or where it is easiest/correct
to fix.  [~jwills] or [~tomwhite] feedback would be welcome.
> [1] -
> [2] -

This message was sent by Atlassian JIRA

View raw message