Github user shuai-xu commented on the issue:
https://github.com/apache/flink/pull/4911
@tillrohrmann, Yes, the Resource is a little too generic and prone to
typos. However, the resource are various and closely related to the
platform(YARN/MESOS), only a GPUResource and FPGAResource may not satisfy
user's need. For example, we have at lease two types of FPGA resources in our
cluster. And it could consider the users who need to specify extended resources
as advanced users. General users only need to know vcore and memory, which are
already defined in ResurceSpec. Advanced users should be familiar with not only
flink but also the resource platform. They should know the resources types
YARN/MESOS supports. And, If flink resource manager passes all the extended
resource to YARN/MESOS when starting a container, it need not change when
adding a new resource type only if YARN/MESOS can recognize it from extended
resources. There has to be a compromise between extendibility and ease of use.
I suggest we can add a general GPUResource and FPGAResource for general use
while st
ill keeping the Resource for extension. Does this make sense?
---
