[
https://issues.apache.org/jira/browse/YARN-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664537#comment-13664537
]
Alejandro Abdelnur commented on YARN-710:
-----------------------------------------
If we don't want to support compatibility of disk serialization for some
records, how do you identify the supported ones without a tag interface? I
would expect the write call to fail if it is not supported the the given record.
I'm OK with having an additional public API class to do the ser/deser of
'supported' records. Still I think such class should delegate to the
RecordFactory as the record factory knows about the underlaying implementation
and can process the ser/deser leveraging the implementation.
> Add to ser/deser methods to RecordFactory
> -----------------------------------------
>
> Key: YARN-710
> URL: https://issues.apache.org/jira/browse/YARN-710
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api
> Affects Versions: 2.0.4-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: YARN-710.patch
>
>
> I order to do things like AMs failover and checkpointing I need to serialize
> app IDs, app attempt IDs, containers and/or IDs, resource requests, etc.
> Because we are wrapping/hiding the PB implementation from the APIs, we are
> hiding the built in PB ser/deser capabilities.
--
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
