Junping Du commented on YARN-2347:

Thanks for review and comments, [~zjshen]! That's good point and I agree it is 
possible to be used in future by other applications. However, before the real 
requirements comes in (as applications don't have to follow our practice in 
YARN for versioning), let's play safe to keep it as private as it is mostly 
used among YARN and built-in MR components. We can easily to make an API public 
from private in future, but making a public API back to private (or change 
interfaces) should never happen. So, IMO, it is better to keep it as private at 
this moment. We can open a separated JIRA (and work) to discuss more if you 
have a strong feeling to public it. Thoughts?

> Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in 
> yarn-server-common
> ----------------------------------------------------------------------------------------
>                 Key: YARN-2347
>                 URL: https://issues.apache.org/jira/browse/YARN-2347
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: YARN-2347-v2.patch, YARN-2347-v3.patch, 
> YARN-2347-v4.patch, YARN-2347-v5.patch, YARN-2347.patch
> We have similar things for version state for RM, NM, TS (TimelineServer), 
> etc. I think we should consolidate them into a common object.

This message was sent by Atlassian JIRA

Reply via email to