crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Tzolov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CRUNCH-185) Make the MemPipeline#done return a PipelineResult with the Counters inside.
Date Wed, 27 Mar 2013 00:57:15 GMT

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

Christian Tzolov updated CRUNCH-185:
------------------------------------

    Attachment: CRUNCH-185-all.patch
                CRUNCH-185-2.patch

ah, it should be void indeed. In addition i've removed some redundan code and made the runAsynch()
response consistent with run().
                
> Make the MemPipeline#done return a PipelineResult with the Counters inside.
> ---------------------------------------------------------------------------
>
>                 Key: CRUNCH-185
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-185
>             Project: Crunch
>          Issue Type: Bug
>    Affects Versions: 0.5.0
>            Reporter: Christian Tzolov
>            Assignee: Christian Tzolov
>            Priority: Minor
>         Attachments: CRUNCH-185-2.patch, CRUNCH-185-all.patch, CRUNCH-185.patch
>
>
> The MRPipeline exposes the job counters via the PipelineResult. The MemPipeline behaves
differently. It always returns an EMPTY PipelineResult and exposes a static getCounters()
method. 
> To make both implementations behave alike the MemPipeline should return a single-staged
PipelineResult containing the Counters. 
> Also the MemPipeline should provide a mechanism to reset the Counters. At the moment
there is no other mechanism to reset but restarting the application.  

--
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

Mime
View raw message