[
https://issues.apache.org/jira/browse/TEZ-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142220#comment-15142220
]
Siddharth Seth commented on TEZ-3029:
-------------------------------------
bq. Why add a new DAGInfo when there is an existing DagIdentifier that provides
the necessary information. DagIdentifier is already a public facing entity for
users to dag related information. What is the need to add another entity?
DAGInfo will eventually contain more information - state, vertex level info etc
will all go in here
bq. The ServicePluginErrorDefaults/ServicePluginError pattern seems strange ...
User defined errors as enums. The implementation does not have to be a Enum, it
can very simply be a regular class - but must return an enum. Having a lot of
functionality in such an implementation is not expected. The method would
simply expose an Enum if they were extendable.
> Add an onError method to service plugin contexts
> ------------------------------------------------
>
> Key: TEZ-3029
> URL: https://issues.apache.org/jira/browse/TEZ-3029
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-3029.1.txt, TEZ-3029.2.txt, TEZ-3029.3.txt
>
>
> This is to indicate errors which may occur while running threads etc.
> One bit to be careful about is that this introduces two means of reporting
> errors - which has been challenging to handle in the past for
> Input/Processor/OutputContext - so whether to do this or not needs to be
> thought through.
> TaskSchedulerContext already has this method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
