[jira] [Commented] (CRUNCH-55) MemPipeline doesn't correctly initialize PTypes MapFns

["Gabriel Reid (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CRUNCH-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453756#comment-13453756 ] 

Gabriel Reid commented on CRUNCH-55:
------------------------------------

I believe I misreported this issue -- the initialize only needs to be called if the PType is being used for actual reading or writing. Will get a closer look at this one once I'm better connected (I've only got mobile phone connectivity ATM), as this is linked to another issue that I was encountering with writable ptypes. 
                
> MemPipeline doesn't correctly initialize PTypes MapFns
> ------------------------------------------------------
>
>                 Key: CRUNCH-55
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-55
>             Project: Crunch
>          Issue Type: Bug
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Gabriel Reid
>         Attachments: WritableIT.java
>
>
> When a MemPipeline is run, the setContext method (and therefore also the initialize method) is not called on the MapFns in PTypes. On PTypes MapFns that rely on logic in the initialize method, this causes the pipeline to crash.
> This can be shown by using PTable#join with Writable values -- a NullPointerException occurs due to the state of the PType input or output MapFn not being fully set up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira