Page History

...

In order to support the above, hive metastore needs to be enhanced to have the concept of a cluster.
The existing thrift API's will continue to work as if the user is trying to access the default cluster.
New APIs will be added which take the cluster as a new parameter. Almost all the existing APIs will be
enhanced to support this. The behavior will be the same as if, the user issued the command 'USE CLUSTER <CLUSTERNAME>

If the user does not intend of use multiple clusters, there should be no change in the behavior of hive commands, and all the
existing thrift APIs should continue to work. There may be some very minor changes required: Cluster -> JobTracker mapping (with only
a single entry) and all table's primary cluster need to some pre-defined fixed cluster. If that is a problem, we can even add a new
configuration parameter, hive.disable.clusters, which will make this whole multi-cluster business transparent to the end users.