[
https://issues.apache.org/jira/browse/YARN-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730673#comment-15730673
]
Wangda Tan commented on YARN-5012:
----------------------------------
Think again about this: even if we can break compatibility in 3.0, that doesn't
mean we should do that. So I would prefer to keep it compatible and not do it
now.
Unassign myself from the JIRA and downgrade priority.
> Upgrade fields of o.a.h.y.api.records.Resource from int32 to int64
> ------------------------------------------------------------------
>
> Key: YARN-5012
> URL: https://issues.apache.org/jira/browse/YARN-5012
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
>
> This is to track fixes for 3.x releases. In YARN-4844 we fix this problem in
> an API compatible way: adding new int64 APIs and keeps old int32 APIs.
> Since we can break API compatibility in 3.x releases, we can make changes on
> old protocols directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
