junyan-ling commented on PR #187: URL: https://github.com/apache/yunikorn-release/pull/187#issuecomment-2651622503
> Looks like this one is depending on #186, lets get that one reviewed and merged first. And any particular reason using golang here? I thought python might be more straightforward in such use case. There is no constraint in what language to use in this repo just to be clear, if that's the reason you choose golang. Was assuming in main.go file in https://github.com/apache/yunikorn-release/pull/186/files we'll need to add some logic later to call the go functions such as `UpgradeSchedulerPerConfig` and `SetNodeScalePerConfig ` implemented in this PR, so I thought using golang would be more straightforward. If the language is no restriction and brings easier implementation I can switch to Python in the current PR or later PRs. -- 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. To unsubscribe, e-mail: reviews-unsubscr...@yunikorn.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
