[
https://issues.apache.org/jira/browse/CRUNCH-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Sharma updated CRUNCH-55:
-------------------------------
Attachment: WritableIT.java
I think this is not just with MemPipeline, MRPipelines also have the same
issue. I have attached a testcase that has Ptype doing things in initialize.
This one fails for both pipelines.
Can someone tell me if my test case is right ?
> 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
