[ 
https://issues.apache.org/jira/browse/TEZ-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205794#comment-15205794
 ] 

Bikas Saha commented on TEZ-3181:
---------------------------------

Do we need this? Could we use 0.7 parser for 0.7 jobs and 0.8 parser for 0.8 
jobs. My concern is that we use 0.8 parser, ignore some fields that are needed 
while parsing, and then the analyzers will fail or worse produce wrong results. 
This could be because analyzers are expecting a certain structure and that has 
changed in the data.

> History parser : Handle invalid/unsupported history event types gracefully
> --------------------------------------------------------------------------
>
>                 Key: TEZ-3181
>                 URL: https://issues.apache.org/jira/browse/TEZ-3181
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-3181.1.patch
>
>
> TEZ-2581 changed/renamed some of HistoryEventType. This causes parser to 
> throw exception when trying to parse 0.7.x ATS data with 0.8.x parser.
> {noformat}
>  Exception in thread "main" java.lang.IllegalArgumentException: No enum 
> constant 
> org.apache.tez.dag.history.HistoryEventType.VERTEX_PARALLELISM_UPDATED
>        at java.lang.Enum.valueOf(Enum.java:238)
>        at 
> org.apache.tez.dag.history.HistoryEventType.valueOf(HistoryEventType.java:21)
>        at 
> org.apache.tez.history.parser.datamodel.VertexInfo.<init>(VertexInfo.java:117)
>        at 
> org.apache.tez.history.parser.datamodel.VertexInfo.create(VertexInfo.java:159)
>        at 
> org.apache.tez.history.parser.ATSFileParser.processVertices(ATSFileParser.java:98)
>        at 
> org.apache.tez.history.parser.ATSFileParser.parseATSZipFile(ATSFileParser.java:202)
>        at 
> org.apache.tez.history.parser.ATSFileParser.getDAGData(ATSFileParser.java:70)
> {noformat}
> Long term fix is to have versioning support (TEZ-3179) in ATS data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to