Hdfs service should be mandatory for HBase and Hive about registry

[priyank5485]

@shahsank3t Can you or someone familiar with UI look in to this?
@HeartSaVioR I see that we are packaing hdfs-site.xml and core-site.xml with the topology jar if we have just HBase sink in the topology. Just curious about the logic used to pick hdfs-site and core-site if we have two hdfs services(both from different service pools) added to the same environment? Will it pick the right one?

[HeartSaVioR]

@priyank5485
No we can't determine which is the right one, so the services which rely on configuration file like HDFS, HBase, and Hive should be selected only once.

Maybe better to prevent selecting same service multiple time in an environment until we support multi-clusters for all services properly. That may be an unnecesary limitation for other services, but safest way to avoid that issue.

We might also want to force selecting cluster for each component in order to provide corresponding configurations while deploying.
(Maybe also better to change some fields which are dependent on cluster to be read-only.)

cc. @harshach @shahsank3t

[HeartSaVioR]

@priyank5485
Btw I guess this issue is filed to wrong project. :) Did you intend to file this issue to the Streamline project?

[priyank5485]

@HeartSaVioR you are right. will refile in streamline