Member since
02-13-2020
7
Posts
0
Kudos Received
1
Solution
02-19-2020
08:59 AM
Excellent. This is the solution i've applied. But i was not able to explain why it does not work anymore with cdh6. Thanks
... View more
02-13-2020
01:07 AM
Hello everyone, need help please. when i execute the following request on the impala-shell (Cloudera cdh5.16) CREATE TABLE FCT_OC_ACTIVE_ALARMS_COUNTERS ( TIME TIMESTAMP NOT NULL ENCODING RLE, OPERATIONCONTEXTID BIGINT NOT NULL ENCODING RLE, SEVERITYID BIGINT NOT NULL ENCODING RLE, ALARMTYPEID BIGINT NOT NULL, PROBABLECAUSEID BIGINT NOT NULL, SPECIFICPROBLEMSID BIGINT, MANAGEDOBJECTNAME STRING NOT NULL, YEARMONTH INT NOT NULL, NEXTDELTATIME TIMESTAMP, AOACKNOWLEDGED BIGINT, AOHANDLED BIGINT, AONOTHANDLED BIGINT, AOOUTSTANDING BIGINT, UPDATE_TIMESTAMP TIMESTAMP, PRIMARY KEY(TIME, OPERATIONCONTEXTID, SEVERITYID, ALARMTYPEID, PROBABLECAUSEID, MANAGEDOBJECTNAME, SPECIFICPROBLEMSID, YEARMONTH) ) PARTITION BY RANGE (YEARMONTH) ( PARTITION VALUE = 202001 ) STORED AS KUDU it works perfectly. but when i execute the same on impala-shell (Cloudera cdh 6.3.2) i get the following error: ERROR: ImpalaRuntimeException: Error creating Kudu table 'impala::ci_inta_fas_oss_installer_cdh6.FCT_OC_ACTIVE_ALARMS_COUNTERS' CAUSED BY: ImpalaRuntimeException: Kudu PRIMARY KEY columns must be specified as the first columns in the table (expected leading columns ('time', 'operationcontextid', 'severityid', 'alarmtypeid', 'probablecauseid', 'managedobjectname', 'specificproblemsid', 'yearmonth') but found ('time', 'operationcontextid', 'severityid', 'alarmtypeid', 'probablecauseid', 'specificproblemsid', 'managedobjectname', 'yearmonth')) Did i mess something in my configuration on cdh 6.3 ?
... View more
Labels:
- Labels:
-
Apache Impala
-
Apache Kudu