kingamarton commented on pull request #22: URL: https://github.com/apache/incubator-yunikorn-scheduler-interface/pull/22#issuecomment-657493356
I thing I get the point mentioned by @wilfred-s. I agree that there is no request in most of the cases, but we added this new field to the UpdateResponse, because there are handled the other Application related changes. I had an another idea to create a new object and send it back instead of creating a full UpdateRequest with only one field populated, but that way I will break the contract. Related your comment regarding the "3 ways of communicating these updates". The other updates are for different object types, I don't this is a good idea to mix them. I would handle the application separately from the OutstandingResourceResource and contanerSchedulingState update. @wilfred-s do you have any better idea of handling this? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
