Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
May 14, 2024 2:57:48 AM
May 13, 2024 6:50:57 AM
The problem occurs when running a reload from Data Gateway to a Cloudera DB (Cloudera Hive).
The reload is completed correctly, but the fields are imported with aliases. This means that the reload imports the fields as 'TableName.FieldName' instead of importing them as just 'FieldName'.
For example, with this script:
LOAD meter_id,
Field1,
Field2,
Field3;
[meter_attribute]:
SELECT "meter_id",
"Field1",
"Field2",
"Field3"
FROM internaldb."meter_attribute";
Fields are imported as: meter_attribute.Field1, meter_attribute.Field2, meter_attribute.Field3.
The problem can be fixed adding the row EnableUniqueColumnName=0 to the connection string.
{ "SyntaxId": "ClouderaHive", "DisplayName": "Cloudera Hive syntax", "DelimiterStart": "`", "DelimiterEnd": "`", "DataPreviewSelectTemplate": "SELECT ${COLUMN_LIST} FROM ${TABLE_NAME} ${FILTER} LIMIT ${LIMIT_VALUE}", "DatabaseTerm": "catalog", "OwnerTerm": "schema" }
QB-26342