How can I use Hive and Spark on Amazon EMR to query an AWS Glue Data Catalog that's in a different AWS account?
I want to access and query another account's AWS Glue Data Catalog using Apache Hive and Apache Spark in Amazon EMR.
"I want to access and query another account's AWS Glue Data Catalog using Apache Hive and Apache Spark in Amazon EMR.Short descriptionYou can dynamically access Data Catalog in different accounts by specifying the property aws.glue.catalog.separator in your Hive or Spark configurations. Additionally, you can access a specific Data Catalog in another account by specifying the property  hive.metastore.glue.catalogid in your Hive or Spark configurations.ResolutionIf you didn't grant cross-account access to AWS Glue, then follow the steps in Grant cross-account access to set it up. Be sure that the Amazon Simple Storage Service (Amazon S3) bucket that the AWS Glue tables point to is configured for cross-account access. For more information, see How can I set up cross-account access for Amazon EMRFS?Dynamically access Data Catalog in different accountsApply configuration changes to a new clusterWhen you launch an EMR cluster, add a configuration object similar to the following object. For more information, see Configure applications when you create a cluster.[{    "Classification": "hive-site",    "Properties": {        "aws.glue.catalog.separator": "/",        "hive.metastore.client.factory.class": "com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory"    }}, {    "Classification": "spark-hive-site",    "Properties": {        "aws.glue.catalog.separator": "/",        "hive.metastore.client.factory.class": "com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory"    }}]Apply configuration changes to a running clusterOpen the Amazon EMR console.In the cluster list, under Cluster Id, choose the active cluster that you want to reconfigure.In the cluster details page, choose the Applications tab.In the applications details page, scroll down to Instance group configurations.Select the instance group, and then choose Reconfigure.In the next screen, choose Add new configuration, and then enter the following:For Classification: hive-siteFor Property: aws.glue.catalog.separatorFor Value: /For Classification: hive-siteFor Property: hive.metastore.client.factory.classFor Value: com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactoryFor Classification: spark-hive-siteFor Property: aws.glue.catalog.separatorFor Value: /For Classification: spark-hive-siteFor Property: hive.metastore.client.factory.classFor Value: com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactoryCheck Apply this configuration to all active instance groups, and then choose Save changes. For more information, see Reconfigure an instance group in a running cluster.Query tables in another AWS accountNote: In Amazon EMR 6.5, pass the configuration property spark.sql.catalogImplementation=hive when running Spark jobs. For more information, see Dynamically loading Spark properties in the Apache Spark documentation.To query a table that's in a different AWS account, specify the account number in the query. The account number is the same as the catalog ID. For example, to query demodb.tab1 in account 111122223333 in Hive, run the following command:SELECT * FROM `111122223333/demodb.tab1` LIMIT 5;Spark example (run this in the spark-submit script, or as a notebook shell command):spark.sql("SELECT * FROM `111122223333/demodb`.tt1 LIMIT 5").show()You can also join tables across two catalogs.Hive example:SELECT * FROM `111122223333/demodb.tab1` t1 INNER JOIN `444455556666/demodb.tab2` t2 ON t1.col1 = t2.col2Spark example (run this in the spark-submit script, or as a notebook shell command):spark.sql(SELECT * FROM `111122223333/demodb.tab1` t1 INNER JOIN `444455556666/demodb.tab2` t2 ON t1.col1 = t2.col2).show()Access a specific Data Catalog in another accountApply configuration changes to a new clusterWhen you launch an EMR cluster, add a configuration object similar to the following object. For more information, see Configure applications when you create a cluster.[{    "Classification": "hive-site",    "Properties": {        "hive.metastore.client.factory.class": "com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory",        "hive.metastore.glue.catalogid": "account-id"    }}, {    "Classification": "spark-hive-site",    "Properties": {        "hive.metastore.client.factory.class": "com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory",        "hive.metastore.glue.catalogid": "account-id"    }}]Apply configuration changes to a running clusterOpen the Amazon EMR console.In the cluster list, under Cluster Id, choose the active cluster that you want to reconfigure.In the cluster details page, choose the Applications tab.In the applications details page, scroll down to Instance group configurations.Select the instance group, and then choose ReconfigureIn the next screen, choose Add new configuration, and then enter the following:For Classification: hive-siteFor Property: hive.metastore.glue.catalogidFor Value: account-idFor Classification: hive-siteFor Property: hive.metastore.client.factory.classFor Value: com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactoryFor Classification: spark-hive-siteFor Property: hive.metastore.glue.catalogidFor Value: account-idFor Classification: spark-hive-siteFor Property: hive.metastore.client.factory.classFor Value: com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactoryCheck Apply this configuration to all active instance groups, and then choose Save changes. For more information, please see Reconfigure an instance group in a running cluster.Query tables in another AWS accountTo query tables that are stored in the specified AWS Glue Data Catalog, you can run the following commands. For example, to query demodb.tab1:In Hive, run the following command:SELECT * FROM `demodb.tab1` LIMIT 5;Spark example (run this in the spark-submit script, or as a notebook shell command):spark.sql("SELECT * FROM `demodb`.tt1 LIMIT 5").show()Follow"