Karthik Kambatla / Arun Suresh,
Missed your last comment somehow, apologize for the last reply. Since this is not included by branch-2.8, so we should have enough time to change it.
I want to revert the change because two part:
1) It makes a stable API inherit from an unstable API, which is very confusing. Even if we don't want user to use the AbstractRR, but it is unavoidable. According to API definition, user should write code like:
AbstractResourceRequest r = new ResourceRequest(...);
Apparently we don't want user to do things like this because AbstractRR could be changed.
2) Most importantly, it is not necessary.
YARN-5774 only requires scheduler returns normalized resource instead of update resource inside a given resource request. To me, we should avoid changing user-facing API because of internal implementation, this change is completely avoidable. I suggest to keep the original API.