VERIFY_HADOOP_CONF_DIR
Verifies that the Hadoop configuration that is used to access HDFS is valid on all Vertica nodes. The configuration is valid if:
- all required configuration files are found on the path defined by the HadoopConfDir configuration parameter
- all properties needed by Vertica are set in those files
This function does not attempt to validate the settings of those properties; it only verifies that they have values.
It is possible for Hadoop configuration to be valid on some nodes and invalid on others. The function reports a validation failure if the value is invalid on any node; the rest of the output reports the details.
Syntax
VERIFY_HADOOP_CONF_DIR( )
Parameters
This function has no parameters.
Privileges
This function does not require privileges.
Examples
The following example shows the results when the Hadoop configuration is valid.
=> SELECT VERIFY_HADOOP_CONF_DIR(); verify_hadoop_conf_dir ------------------------------------------------------------------- Validation Success v_vmart_node0001: HadoopConfDir [PG_TESTOUT/config] is valid v_vmart_node0002: HadoopConfDir [PG_TESTOUT/config] is valid v_vmart_node0003: HadoopConfDir [PG_TESTOUT/config] is valid v_vmart_node0004: HadoopConfDir [PG_TESTOUT/config] is valid (1 row)
In the following example, the Hadoop configuration is valid on one node, but on other nodes a needed value is missing.
=> SELECT VERIFY_HADOOP_CONF_DIR(); verify_hadoop_conf_dir ------------------------------------------------------------------- Validation Failure v_vmart_node0001: HadoopConfDir [PG_TESTOUT/test_configs/config] is valid v_vmart_node0002: No fs.defaultFS parameter found in config files in [PG_TESTOUT/config] v_vmart_node0003: No fs.defaultFS parameter found in config files in [PG_TESTOUT/config] v_vmart_node0004: No fs.defaultFS parameter found in config files in [PG_TESTOUT/config] (1 row)