[
    {
        "desc": "The user that this service's processes should run as.",
        "display_name": "System User",
        "name": "process_username",
        "value": "hive"
    },
    {
        "desc": "Directory containing auxiliary JARs used by Hive. This should be a directory location and not a classpath containing one or more JARs. This directory must be created and managed manually on Hive CLI or HiveServer2 host.",
        "display_name": "Hive Auxiliary JARs Directory",
        "name": "hive_aux_jars_path_dir",
        "value": null
    },
    {
        "desc": "Password for Hive Metastore database",
        "display_name": "Hive Metastore Database Password",
        "name": "hive_metastore_database_password",
        "value": ""
    },
    {
        "desc": "The password for the HiveServer2 TLS/SSL Certificate Trust Store File. Note that this password is not required to access the trust store: this field can be left blank. This password provides optional integrity checking of the file. The contents of trust stores are certificates, and certificates are public information.",
        "display_name": "HiveServer2 TLS/SSL Certificate Trust Store Password",
        "name": "hiveserver2_truststore_password",
        "value": null
    },
    {
        "desc": "Name of the Sentry service that this Hive service instance depends on. If selected, Hive uses this Sentry service to look up authorization privileges. Before enabling Sentry, read the requirements and configuration steps in <a class=\"bold\" href=\"http://tiny.cloudera.com/sentry-service-cm5\" target=\"_blank\">Setting Up The Sentry Service<i class=\"externalLink\"></i></a>.",
        "display_name": "Sentry Service",
        "name": "sentry_service",
        "value": null
    },
    {
        "desc": "Directory name where Hive Metastore's database is stored (only for Derby)",
        "display_name": "Hive Metastore Derby Path",
        "name": "hive_metastore_derby_path",
        "value": "/var/lib/hive/cloudera_manager/derby/metastore_db"
    },
    {
        "desc": "Hive warehouse directory is the location in HDFS where Hive's tables are stored. Note that Hive's default value for its warehouse directory is '/user/hive/warehouse'.",
        "display_name": "Hive Warehouse Directory",
        "name": "hive_warehouse_directory",
        "value": "/user/hive/warehouse"
    },
    {
        "desc": "The password for the HiveServer2 JKS keystore file.",
        "display_name": "HiveServer2 TLS/SSL Server JKS Keystore File Password",
        "name": "hiveserver2_keystore_password",
        "value": null
    },
    {
        "desc": "<p>\nConfigures the rules for event tracking and coalescing. This feature is\nused to define equivalency between different audit events. When\nevents match, according to a set of configurable parameters, only one\nentry in the audit list is generated for all the matching events.\n</p>\n\n<p>\nTracking works by keeping a reference to events when they first appear,\nand comparing other incoming events against the \"tracked\" events according\nto the rules defined here.\n</p>\n\n<p>Event trackers are defined in a JSON object like the following:</p>\n\n<pre>\n{\n  \"timeToLive\" : [integer],\n  \"fields\" : [\n    {\n      \"type\" : [string],\n      \"name\" : [string]\n    }\n  ]\n}\n</pre>\n\n<p>\nWhere:\n</p>\n\n<ul>\n  <li>timeToLive: maximum amount of time an event will be tracked, in\n  milliseconds. Must be provided. This defines how long, since it's\n  first seen, an event will be tracked. A value of 0 disables tracking.</li>\n\n  <li>fields: list of fields to compare when matching events against\n  tracked events.</li>\n</ul>\n\n<p>\nEach field has an evaluator type associated with it. The evaluator defines\nhow the field data is to be compared. The following evaluators are\navailable:\n</p>\n\n<ul>\n  <li>value: uses the field value for comparison.</li>\n\n  <li>userName: treats the field value as a userNname, and ignores any\n  host-specific data. This is useful for environment using Kerberos,\n  so that only the principal name and realm are compared.</li>\n</ul>\n\n<p>\nThe following is the list of fields that can be used to compare Hive events:\n</p>\n\n<ul>\n  <li>username: the user performing the action.</li>\n  <li>ipAddress: the IP from where the request originated.</li>\n  <li>operation: the Hive operation being performed.</li>  \n  <li>databaseName: the database affected by the operation.</li>\n  <li>tableName: the table affected by the operation.</li>  \n</ul>\n\n",
        "display_name": "Audit Event Tracker",
        "name": "navigator_event_tracker",
        "value": null
    },
    {
        "desc": "Action to take when the audit event queue is full. Drop the event or shutdown the affected process.",
        "display_name": "Audit Queue Policy",
        "name": "navigator_audit_queue_policy",
        "value": "DROP"
    },
    {
        "desc": "HDFS path to the global policy file for Sentry authorization. This should be a relative path (and not a full HDFS URL). The global policy file must be in Sentry policy file format.",
        "display_name": "Sentry Global Policy File",
        "name": "hive_sentry_provider_resource",
        "value": "/user/hive/sentry/sentry-provider.ini"
    },
    {
        "desc": "The location on disk of the trust store, in .jks format, used to confirm the authenticity of TLS/SSL servers that HiveServer2 might connect to. This is used when HiveServer2 is the client in a TLS/SSL connection. This trust store must contain the certificate(s) used to sign the service(s) being connected to. If this parameter is not provided, the default list of well-known certificate authorities is used instead.",
        "display_name": "HiveServer2 TLS/SSL Certificate Trust Store File",
        "name": "hiveserver2_truststore_file",
        "value": null
    },
    {
        "desc": "Max number of reducers to use. If the configuration parameter Hive Reduce Tasks is negative, Hive will limit the number of reducers to the value of this parameter.",
        "display_name": "Hive Max Reducers",
        "name": "hive_max_reducers",
        "value": "1099"
    },
    {
        "desc": "Prevent Metastore operations in the event of schema version incompatibility. Consider setting this to true to reduce probability of schema corruption during Metastore operations. Note that setting this property to true will also set datanucleus.autoCreateSchema property to false and datanucleus.fixedDatastore property to true. Any values set in Cloudera Manager for these properties will be overridden.",
        "display_name": "Strict Hive Metastore Schema Validation",
        "name": "hive_metastore_schema_verification",
        "value": "true"
    },
    {
        "desc": "Encrypt communication between clients and HiveServer2 using Transport Layer Security (TLS) (formerly known as Secure Socket Layer (SSL)).",
        "display_name": "Enable TLS/SSL for HiveServer2",
        "name": "hiveserver2_enable_ssl",
        "value": "false"
    },
    {
        "desc": "Type of Hive Metastore database. Note that Derby is not recommended and Cloudera Impala does not support Derby.",
        "display_name": "Hive Metastore Database Type",
        "name": "hive_metastore_database_type",
        "value": "mysql"
    },
    {
        "desc": "Maximum size of audit log file in MB before it is rolled over.",
        "display_name": "Maximum Audit Log File Size",
        "name": "navigator_audit_log_max_file_size",
        "value": "100"
    },
    {
        "desc": "For advanced use only, a string to be inserted into <strong>hive-site.xml</strong>. Applies to configurations of all roles in this service except client configuration.",
        "display_name": "Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml",
        "name": "hive_service_config_safety_valve",
        "value": null
    },
    {
        "desc": "Maximum number of rolled over audit logs to retain. The logs will not be deleted if they contain audit events that have not yet been propagated to Audit Server.",
        "display_name": "Number of Audit Logs to Retain",
        "name": "navigator_audit_log_max_backup_index",
        "value": "10"
    },
    {
        "desc": "The URI of the LDAP server to use if LDAP authentication is enabled. The URI must be prefixed with ldap:// or ldaps://. Usernames and passwords will go over the wire in the clear unless an \"ldaps://\" URI is specified. The URI can optionally specify the port, for example: ldaps://ldap_server.example.com:636.",
        "display_name": "LDAP URI",
        "name": "hiveserver2_ldap_uri",
        "value": null
    },
    {
        "desc": "Port number of Hive Metastore database",
        "display_name": "Hive Metastore Database Port",
        "name": "hive_metastore_database_port",
        "value": "3306"
    },
    {
        "desc": "Name of the ZooKeeper service that this Hive service instance depends on.",
        "display_name": "ZooKeeper Service",
        "name": "zookeeper_service",
        "value": null
    },
    {
        "desc": "Host name of Hive Metastore database",
        "display_name": "Hive Metastore Database Host",
        "name": "hive_metastore_database_host",
        "value": "localhost"
    },
    {
        "desc": "List of users that are allowed to bypass Sentry Authorization in the Hive metastore. These are usually service users that already ensure that all activity has been authorized, such as hive and impala. Only applies when Hive is using Sentry Service.",
        "display_name": "Bypass Sentry Authorization Users",
        "name": "sentry_metastore_service_users",
        "value": "hive,impala,hue,hdfs"
    },
    {
        "desc": "When set, this value will be appended to all usernames before authenticating with the LDAP server. For example, if this parameter is set to \"my.domain.com\" and the user authenticating is \"mike\", then \"mike@my.domain.com\" will be passed to the LDAP server. If this field is unset, the username will remain unaltered before being passed to the LDAP server. LDAP Domain is most useful when authenticating against an Active Directory server. This parameter is mutually exclusive with LDAP BaseDN.",
        "display_name": "LDAP Domain",
        "name": "hiveserver2_ldap_domain",
        "value": null
    },
    {
        "desc": "The path to the TLS/SSL keystore file containing the server certificate and private key used for TLS/SSL. Used when HiveServer2 is acting as a TLS/SSL server. The keystore must be in JKS format.",
        "display_name": "HiveServer2 TLS/SSL Server JKS Keystore File Location",
        "name": "hiveserver2_keystore_path",
        "value": null
    },
    {
        "desc": "Automatically create or upgrade tables in the Hive Metastore database when needed. Consider setting this to false and managing the schema manually.",
        "display_name": "Auto Create and Upgrade Hive Metastore Database Schema",
        "name": "hive_metastore_database_auto_create_schema",
        "value": "false"
    },
    {
        "desc": "For advanced use only, key-value pairs (one on each line) to be inserted into a role's environment. Applies to configurations of all roles in this service except client configuration.",
        "display_name": "Hive Service Environment Advanced Configuration Snippet (Safety Valve)",
        "name": "hive_service_env_safety_valve",
        "value": null
    },
    {
        "desc": "Path to the directory where audit logs will be written. The directory will be created if it doesn't exist.",
        "display_name": "Audit Log Directory",
        "name": "audit_event_log_dir",
        "value": "/var/log/hive/audit"
    },
    {
        "desc": "Kerberos principal used by all roles of this service.",
        "display_name": "Kerberos Principal",
        "name": "kerberos_princ_name",
        "value": "hive"
    },
    {
        "desc": "When checked, LDAP-based authentication for users is enabled. This option is incompatible with Kerberos authentication for Hive Server 2 at this time.",
        "display_name": "Enable LDAP Authentication",
        "name": "hiveserver2_enable_ldap_auth",
        "value": "false"
    },
    {
        "desc": "Name of Hive Metastore database",
        "display_name": "Hive Metastore Database Name",
        "name": "hive_metastore_database_name",
        "value": "metastore"
    },
    {
        "desc": "The class to use in Sentry authorization for user to group mapping. Sentry authorization may be configured to use either Hadoop user to group mapping or local groups defined in the policy file. Hadoop user to group mapping may be configured in the Cloudera Manager HDFS service configuration page under the Security section.",
        "display_name": "Sentry User to Group Mapping Class",
        "name": "hive_sentry_provider",
        "value": "org.apache.sentry.provider.file.HadoopGroupResourceAuthorizationProvider"
    },
    {
        "desc": "Use Sentry to enable role-based, fine-grained authorization. This configuration enables Sentry using policy files. To enable Sentry using the Sentry service instead, add the Sentry service as a dependency to the Hive service. <strong>The Sentry service provides concurrent and secure access to authorization policy metadata and is the recommended option for enabling Sentry. </strong> Sentry is supported only on CDH 4.4 or later deployments. Before enabling Sentry, read the requirements and configuration steps in <a class=\"bold\" href=\"http://tiny.cloudera.com/sentry-guide-cm5\" target=\"_blank\">Setting Up Hive Authorization with Sentry<i class=\"externalLink\"></i></a>.",
        "display_name": "Enable Sentry Authorization using Policy Files",
        "name": "sentry_enabled",
        "value": "false"
    },
    {
        "desc": "This configuration <strong>overrides</strong> the value set for Hive Proxy User Groups configuration in HDFS service for use by Hive Metastore Server. Specify a comma-delimited list of groups that you want to <strong>allow access to Hive Metastore metadata</strong> and allow the Hive user to impersonate. A value of '*' allows all groups. The default value of empty inherits the value set for Hive Proxy User Groups configuration in the HDFS service.",
        "display_name": "Hive Metastore Access Control and Proxy User Groups Override",
        "name": "hive_proxy_user_groups_list",
        "value": null
    },
    {
        "desc": "Default number of reduce tasks per job. Usually set to a prime number close to the number of available hosts. Ignored when mapred.job.tracker is \"local\". Hadoop sets this to 1 by default, while Hive uses -1 as the default. When set to -1, Hive will automatically determine an appropriate number of reducers for each job.",
        "display_name": "Hive Reduce Tasks",
        "name": "hive_reduce_tasks",
        "value": "-1"
    },
    {
        "desc": "Let the table directories inherit the permission of the Warehouse or Database directory instead of being created with the permissions derived from dfs umask. This allows Impala to insert into tables created via Hive.",
        "display_name": "Hive Warehouse Subdirectories Inherit Permissions",
        "name": "hive_warehouse_subdir_inherit_perms",
        "value": "true"
    },
    {
        "desc": "For advanced use only, a string to be inserted into <strong>core-site.xml</strong>. Applies to configurations of all roles in this service except client configuration.",
        "display_name": "Hive Service Advanced Configuration Snippet (Safety Valve) for core-site.xml",
        "name": "hive_core_site_safety_valve",
        "value": null
    },
    {
        "desc": "The group that this service's processes should run as.",
        "display_name": "System Group",
        "name": "process_groupname",
        "value": "hive"
    },
    {
        "desc": "<p>Event filters are defined in a JSON object like the following:</p>\n\n<pre>\n{\n  \"defaultAction\" : (\"accept\", \"discard\"),\n  \"rules\" : [\n    {\n      \"action\" : (\"accept\", \"discard\"),\n      \"fields\" : [\n        {\n          \"name\" : \"fieldName\",\n          \"match\" : \"regex\"\n        }\n      ]\n    }\n  ]\n}\n</pre>\n\n<p>\nA filter has a default action and a list of rules, in order of precedence.\nEach rule defines an action, and a list of fields to match against the\naudit event.\n</p>\n\n<p>\nA rule is \"accepted\" if all the listed field entries match the audit\nevent. At that point, the action declared by the rule is taken.\n</p>\n\n<p>\nIf no rules match the event, the default action is taken. Actions\ndefault to \"accept\" if not defined in the JSON object.\n</p>\n\n<p>\nThe following is the list of fields that can be filtered for Hive events:\n</p>\n\n<ul>\n  <li>userName: the user performing the action.</li>\n  <li>ipAddress: the IP from where the request originated.</li>\n  <li>operation: the Hive operation being performed.</li>  \n  <li>databaseName: the databaseName for the operation.</li>\n  <li>tableName: the tableName for the operation.</li>\n</ul>\n",
        "display_name": "Audit Event Filter",
        "name": "navigator_audit_event_filter",
        "value": "{\n  \"comment\" : [\n    \"Default filter for Hive services.\",\n    \"Discards events generated by Hive MR jobs in /tmp directory\"\n  ],\n  \"defaultAction\" : \"accept\",\n  \"rules\" : [\n    {\n      \"action\" : \"discard\",\n      \"fields\" : [\n        { \"name\" : \"operation\", \"match\" : \"QUERY\" },\n        { \"name\" : \"objectType\", \"match\" : \"DFS_DIR\"},\n        { \"name\" : \"resourcePath\", \"match\" : \"/tmp/hive-(?:.+)?/hive_(?:.+)?/-mr-.*\" }\n      ]\n    }\n  ]\n}\n"
    },
    {
        "desc": "The health test thresholds of the overall Hive Metastore Server health. The check returns \"Concerning\" health if the percentage of \"Healthy\" Hive Metastore Servers falls below the warning threshold. The check is unhealthy if the total percentage of \"Healthy\" and \"Concerning\" Hive Metastore Servers falls below the critical threshold.",
        "display_name": "Healthy Hive Metastore Server Monitoring Thresholds",
        "name": "hive_hivemetastores_healthy_thresholds",
        "value": "{\"critical\":\"51.0\",\"warning\":\"99.0\"}"
    },
    {
        "desc": "When set, Cloudera Manager will send alerts when the health of this service reaches the threshold specified by the EventServer setting eventserver_health_events_alert_threshold",
        "display_name": "Enable Service Level Health Alerts",
        "name": "enable_alerts",
        "value": "true"
    },
    {
        "desc": "The server name used when defining privilege rules in Sentry authorization. Sentry uses this name as an alias for the Hive service. It does not correspond to any physical server name.",
        "display_name": "Server Name for Sentry Authorization",
        "name": "hive_sentry_server",
        "value": "server1"
    },
    {
        "desc": "Name of the Spark on YARN service that this Hive service instance depends on. If selected and Enable Hive on Spark is set to true, Hive jobs can use the Spark execution engine instead of MapReduce2. Requires that Hive depends on YARN.",
        "display_name": "Spark On YARN Service",
        "name": "spark_on_yarn_service",
        "value": null
    },
    {
        "desc": "The health test thresholds of the overall HiveServer2 health. The check returns \"Concerning\" health if the percentage of \"Healthy\" HiveServer2s falls below the warning threshold. The check is unhealthy if the total percentage of \"Healthy\" and \"Concerning\" HiveServer2s falls below the critical threshold.",
        "display_name": "Healthy HiveServer2 Monitoring Thresholds",
        "name": "hive_hiveserver2s_healthy_thresholds",
        "value": "{\"critical\":\"51.0\",\"warning\":\"99.0\"}"
    },
    {
        "desc": "For advanced use only, a list of configuration properties that will be used by the Service Monitor instead of the current client configuration for the service.",
        "display_name": "Service Monitor Client Config Overrides",
        "name": "smon_client_config_overrides",
        "value": "<property><name>hive.metastore.client.socket.timeout</name><value>60</value></property>"
    },
    {
        "desc": "<p>The configured triggers for this service. This is a JSON formatted list of triggers. These triggers are evaluated as part as the health system. Every trigger expression is parsed, and if the trigger condition is met, the list of actions provided in the trigger expression is executed.</p><p>Each trigger has all of the following fields:</p><ul><li><code>triggerName</code> <strong>(mandatory)</strong> - The name of the trigger. This value must be unique for the specific service. </li><li><code>triggerExpression</code> <strong>(mandatory)</strong> - A tsquery expression representing the trigger. </li><li><code>streamThreshold</code> <strong>(optional)</strong> - The maximum number of streams that can satisfy a condition of a trigger before the condition fires. By default set to 0, and any stream returned causes the condition to fire. </li><li><code>enabled</code> <strong> (optional)</strong> - By default set to 'true'. If set to 'false', the trigger will not be evaluated.</li><li><code>expressionEditorConfig</code> <strong> (optional)</strong> - Metadata for the trigger editor. If present, the trigger should only be edited from the Edit Trigger page; editing the trigger here may lead to inconsistencies.</li></ul></p><p>For example, the followig JSON formatted trigger fires if there are more than 10 DataNodes with more than 500 file-descriptors opened:</p><p><pre>[{\"triggerName\": \"sample-trigger\",\n  \"triggerExpression\": \"IF (SELECT fd_open WHERE roleType = DataNode and last(fd_open) > 500) DO health:bad\",\n  \"streamThreshold\": 10, \"enabled\": \"true\"}]</pre></p><p>See the trigger rules documentation for more details on how to write triggers using tsquery.</p><p>The JSON format is evolving and may change in the future and, as a result, backward compatibility is not guaranteed between releases at this time.</p>",
        "display_name": "Service Triggers",
        "name": "service_triggers",
        "value": "[]"
    },
    {
        "desc": "Instead of talking to Hive Metastore Server for Metastore information, Hive clients will talk directly to the Metastore database.",
        "display_name": "Bypass Hive Metastore Server",
        "name": "hive_bypass_metastore_server",
        "value": "false"
    },
    {
        "desc": "Smaller than this size, Hive uses a single-threaded copy; larger than this size, Hive uses DistCp.",
        "display_name": "Hive Copy Large File Size",
        "name": "hive_exec_copyfile_maxsize",
        "value": "33554432"
    },
    {
        "desc": "User for Hive Metastore database",
        "display_name": "Hive Metastore Database User",
        "name": "hive_metastore_database_user",
        "value": "hive"
    },
    {
        "desc": "Perform DataNucleus validation of metadata during startup. <strong>Note</strong>: when enabled, Hive will log DataNucleus warnings even though Hive will function normally.",
        "display_name": "Hive Metastore Database DataNucleus Metadata Validation",
        "name": "hive_metastore_database_datanucleus_metadata_validation",
        "value": "false"
    },
    {
        "desc": "<strong>Cloudera does not support Hive on Spark in CDH 5.4.</strong> Enable Hive to use Spark for execution even though it is not supported. For evaluation purposes only.",
        "display_name": "Enable Hive on Spark (Unsupported)",
        "name": "enable_hive_on_spark",
        "value": "false"
    },
    {
        "desc": "For advanced use only, a string to be inserted into the client configuration for <strong>navigator.client.properties</strong>.",
        "display_name": "Hive Client Advanced Configuration Snippet (Safety Valve) for navigator.client.properties",
        "name": "navigator_client_config_safety_valve",
        "value": null
    },
    {
        "desc": "The health test thresholds of the overall WebHCat Server health. The check returns \"Concerning\" health if the percentage of \"Healthy\" WebHCat Servers falls below the warning threshold. The check is unhealthy if the total percentage of \"Healthy\" and \"Concerning\" WebHCat Servers falls below the critical threshold.",
        "display_name": "Healthy WebHCat Server Monitoring Thresholds",
        "name": "hive_webhcats_healthy_thresholds",
        "value": "{\"critical\":\"51.0\",\"warning\":\"99.0\"}"
    },
    {
        "desc": "For advanced use only, a string to be inserted into <strong>sentry-site.xml</strong>. Applies to configurations of all roles in this service except client configuration.",
        "display_name": "Hive Service Advanced Configuration Snippet (Safety Valve) for sentry-site.xml",
        "name": "hive_server2_sentry_safety_valve",
        "value": null
    },
    {
        "desc": "Size per reducer. If the input size is 10GiB and this is set to 1GiB, Hive will use 10 reducers.",
        "display_name": "Hive Bytes Per Reducer",
        "name": "hive_bytes_per_reducer",
        "value": "67108864"
    },
    {
        "desc": "Enable collection of audit events from the service's roles.",
        "display_name": "Enable Audit Collection",
        "name": "navigator_audit_enabled",
        "value": "true"
    },
    {
        "desc": "When set, Cloudera Manager will send alerts when this entity's configuration changes.",
        "display_name": "Enable Configuration Change Alerts",
        "name": "enable_config_alerts",
        "value": "false"
    },
    {
        "desc": "Allows URIs when defining privileges in per-database policy files. <strong>Warning:</strong> Typically, this configuration should be disabled. Enabling it would allow database policy file owner (which is generally not Hive admin user) to grant load privileges to any directory with read access to Hive admin user, including databases controlled by other database policy files.",
        "display_name": "Allow URIs in Database Policy File",
        "name": "sentry_allow_uri_db_policyfile",
        "value": "false"
    },
    {
        "desc": "In unsecure mode, setting this property to true will cause the Metastore Server to execute DFS operations using the client's reported user and group permissions. Cloudera Manager will set this for all clients and servers.",
        "display_name": "Set User and Group Information",
        "name": "hive_set_ugi",
        "value": "true"
    },
    {
        "desc": "For advanced use only, a list of derived configuration properties that will be used by the Service Monitor instead of the default ones.",
        "display_name": "Service Monitor Derived Configs Advanced Configuration Snippet (Safety Valve)",
        "name": "smon_derived_configs_safety_valve",
        "value": null
    },
    {
        "desc": "When set, this parameter is used to convert the username into the LDAP Distinguished Name (DN), so that the resulting DN looks like uid=username,X. For example, if this parameter is set to \"ou=People,dc=cloudera,dc=com\", and the username passed in is \"mike\", the resulting authentication passed to the LDAP server will look like \"uid=mike,ou=People,dc=cloudera,dc=com\". This parameter is generally most useful when authenticating against an OpenLDAP server. This parameter is mutually exclusive with LDAP Domain.",
        "display_name": "LDAP BaseDN",
        "name": "hiveserver2_ldap_basedn",
        "value": null
    },
    {
        "desc": "MapReduce jobs are run against this service.",
        "display_name": "MapReduce Service",
        "name": "mapreduce_yarn_service",
        "value": null
    }
]