[
https://issues.apache.org/jira/browse/PIG-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Kommireddi updated PIG-2964:
-------------------------------------
Description: PigStats.JobGraph currently provides an iterator. The
rationale behind providing a List getter is that it simply provides a lot more
methods than an iterator. One could do that in the caller code, but providing
this helper in the API would be beneficial. For eg, a framework that is used by
clients could initiate several pig scripts/store commands at once. At the
framework layer, you might want to be able to determine the number of MR jobs
in total spawned by these multiple scripts and query stats on those. That's
just one use-case, there could be more methods on List that a user could be
interested in. (was: The rationale behind providing a List getter is that it
simply provides a lot more methods than an iterator. One could do that in the
caller code, providing this helper in the API would be beneficial. For eg, a
framework that is used by clients could initiate several pig scripts/store
commands at once. At the framework layer, you might want to be able to
determine the number of MR jobs in total spawned by these multiple scripts and
query stats on those. That's just one use-case, there could be more methods on
List that a user could be interested in. )
> Add helper method getJobList() to PigStats.JobGraph. Extend visibility of
> couple methods on same class
> -------------------------------------------------------------------------------------------------------
>
> Key: PIG-2964
> URL: https://issues.apache.org/jira/browse/PIG-2964
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: Prashant Kommireddi
> Assignee: Prashant Kommireddi
> Fix For: 0.11
>
> Attachments: PIG-2964.patch
>
>
> PigStats.JobGraph currently provides an iterator. The rationale behind
> providing a List getter is that it simply provides a lot more methods than an
> iterator. One could do that in the caller code, but providing this helper in
> the API would be beneficial. For eg, a framework that is used by clients
> could initiate several pig scripts/store commands at once. At the framework
> layer, you might want to be able to determine the number of MR jobs in total
> spawned by these multiple scripts and query stats on those. That's just one
> use-case, there could be more methods on List that a user could be interested
> in.
--
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
