[
https://issues.apache.org/jira/browse/TEZ-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145428#comment-15145428
]
Bikas Saha commented on TEZ-3029:
---------------------------------
>> DAGInfo will eventually contain more information - state, vertex level info
>> etc will all go in here
Can we get more insights please? What is the roadmap here? I would appreciate
it if I can understand where this is going.
>> 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.
That's sounds like a strange pattern. Implementers don't have to be enum's but
they are forced to return an untyped enum. When the differentiation of an Enum
vs Int is that enum provides type safety.
> 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)
