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/08/14 18:58:12 UTC

[jira] [Resolved] (CRUNCH-446) Add null checks for DoFn fields

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

Josh Wills resolved CRUNCH-446.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11.0
                   0.8.4

Pushed to master and 0.8. Thanks Allan!

> Add null checks for DoFn fields
> -------------------------------
>
>                 Key: CRUNCH-446
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-446
>             Project: Crunch
>          Issue Type: Improvement
>            Reporter: Allan Shoup
>            Priority: Minor
>             Fix For: 0.8.4, 0.11.0
>
>         Attachments: CRUNCH-446.2.patch, CRUNCH-446.3.patch, CRUNCH-446.patch
>
>
> DoFn.getConfiguration() gracefully handles the fields being null, but most other methods do not. Adding null checks around all field access within DoFn would make it easier for consumers to write tests for their own function classes because they would not be required to set the context, for instance.



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