AWS emr documentation change
Summary
Minor editorial changes including wording adjustments (e.g. 'see' to 'refer to'), table header clarifications, and terminology updates like 'app master' to 'app primary'
Security assessment
Changes are editorial improvements and terminology updates without any security vulnerability fixes or new security-related content. The IAM role mention remains unchanged except for reference formatting.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-hive.md b/emr/latest/EMR-Serverless-UserGuide/jobs-hive.md index 0011cdd03..e3fcf0e98 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-hive.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-hive.md @@ -9 +9 @@ Hive parametersHive propertiesHive examples -You can run Hive jobs on an application with the `type` parameter set to `HIVE`. Jobs must be compatible with the Hive version compatible with the Amazon EMR release version. For example, when you run jobs on an application with Amazon EMR release 6.6.0, your job must be compatible with Apache Hive 3.1.2. For information on the application versions for each release, see [Amazon EMR Serverless release versions](./release-versions.html). +You can run Hive jobs on an application with the `type` parameter set to `HIVE`. Jobs must be compatible with the Hive version compatible with the Amazon EMR release version. For example, when you run jobs on an application with Amazon EMR release 6.6.0, your job must be compatible with Apache Hive 3.1.2. For information on the application versions for each release, refer to [Amazon EMR Serverless release versions](./release-versions.html). @@ -13 +13 @@ You can run Hive jobs on an application with the `type` parameter set to `HIVE`. -When you use the [`StartJobRun` API](https://docs.aws.amazon.com/emr-serverless/latest/APIReference/API_StartJobRun.html) to run a Hive job, you must specify the following parameters. +When you use the [`StartJobRun` API](https://docs.aws.amazon.com/emr-serverless/latest/APIReference/API_StartJobRun.html) to run a Hive job, specify the following parameters. @@ -47 +47 @@ Use **`executionRoleArn`** to specify the ARN for the IAM role that your applica -If your Hive job reads or writes data to or from other data sources, specify the appropriate permissions in this IAM role. If you don't provide these permissions to the IAM role, your job might fail. For more information, see [Job runtime roles for Amazon EMR Serverless](./security-iam-runtime-role.html). +If your Hive job reads or writes data to or from other data sources, specify the appropriate permissions in this IAM role. If you don't provide these permissions to the IAM role, your job might fail. For more information, refer to [Job runtime roles for Amazon EMR Serverless](./security-iam-runtime-role.html). @@ -92 +92 @@ If you pass the same configuration in an application override and in Hive parame -For more information on declaring configurations at the application level, and overriding configurations during job run, see [Default application configuration for EMR Serverless](./default-configs.html). +For more information on declaring configurations at the application level, and overriding configurations during job run, refer to [Default application configuration for EMR Serverless](./default-configs.html). @@ -96 +96 @@ For more information on declaring configurations at the application level, and o -The following table lists the mandatory properties that you must configure when you submit a Hive job. +The following table lists the mandatory properties that configure when you submit a Hive job. @@ -98 +98 @@ The following table lists the mandatory properties that you must configure when -Setting | Description +Mandatory Hive job properties Setting | Description @@ -105 +105 @@ The following table lists the optional Hive properties and their default values -Setting | Description | Default value +Optional Hive properties and default values Setting | Description | Default value @@ -123 +123 @@ Setting | Description | Default value -`hive.exec.dynamic.partition.mode` | Option that specifies whether you want to use strict mode or non-strict mode. In strict mode, you must specify at least one static partition in case you accidentally overwrite all partitions. In non-strict mode, all partitions are allowed to be dynamic. | `strict` +`hive.exec.dynamic.partition.mode` | Option that specifies whether you want to use strict mode or non-strict mode. In strict mode, specify at least one static partition in case you accidentally overwrite all partitions. In non-strict mode, all partitions are allowed to be dynamic. | `strict` @@ -126 +126 @@ Setting | Description | Default value -`hive.exec.orc.split.strategy` | Expects one of the following values: `BI`, `ETL`, or `HYBRID`. This isn’t a user-level configuration. `BI` specifies that you want to spend less time in split generation as opposed to query execution. `ETL` specifies that you want to spend more time in split generation. `HYBRID` specifies a choice of the above strategies based on heuristics. | `HYBRID` +`hive.exec.orc.split.strategy` | Expects one of the following values: `BI`, `ETL`, or `HYBRID`. This isn’t a user-level configuration. `BI` specifies that you want to spend less time in split generation as opposed to query execution. `ETL` specifies that you want to spend more time in split generation. `HYBRID` specifies a choice of the preceding strategies based on heuristics. | `HYBRID` @@ -169 +169 @@ Setting | Description | Default value -`tez.am.log.level` | The root logging level that EMR Serverless passes to the Tez app master. | `INFO` +`tez.am.log.level` | The root logging level that EMR Serverless passes to the Tez app primary. | `INFO`