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/15 03:08:14 UTC

[jira] [Resolved] (CRUNCH-394) Ensure that the Broadcast configuration in SparkRuntimeContext is never null

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

Josh Wills resolved CRUNCH-394.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8.3
                   0.10.0

> Ensure that the Broadcast configuration in SparkRuntimeContext is never null
> ----------------------------------------------------------------------------
>
>                 Key: CRUNCH-394
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-394
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Josh Wills
>             Fix For: 0.10.0, 0.8.3
>
>         Attachments: CRUNCH-394.patch
>
>
> It looks like it's possible for Spark to recompute some RDDs that get reloaded between output runs. When this happens, the Broadcast<byte[]> field that contains the serialized Configuration object is null b/c we haven't declared an output RDD to run against yet. I added a change to ensure that the serialized Configuration object is always defined, even before we generate any output, to ensure that we don't throw an NPE.



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