Open gsuetugo opened 3 years ago
Hi @gsuetugo, If you use Impala and Kudu the tables definition is as follows but you can adjust for your infrastructure accordingly:
CREATE TABLE DATABASECHANGELOGLOCK (ID INT, LOCKED BOOLEAN, LOCKGRANTED timestamp, LOCKEDBY STRING);
CREATE TABLE DATABASECHANGELOG (ID STRING, AUTHOR STRING, FILENAME STRING, DATEEXECUTED timestamp, ORDEREXECUTED INT, EXECTYPE STRING, MD5SUM STRING, DESCRIPTION STRING, COMMENTS STRING, TAG STRING, LIQUIBASE STRING, CONTEXTS STRING, LABELS STRING, DEPLOYMENT_ID STRING, PRIMARY KEY(ID))
STORED AS KUDU TBLPROPERTIES ('kudu.num_tablet_replicas' = '1');
It seems the author has abandoned this project. So we're on our own.
Hi,
In which part of the code we can overwrite these statements (CREATE TABLE DATABASECHANGELOGLOCK && CREATE TABLE DATABASECHANGELOG) so that they are not created by Liquibase?
Thank you, Javi
Hey,
I'm trying to run the update command on a liquibase 4.3.2 version using the impala driver created by maven command, but gets on the same error:
Unexpected error running Liquibase: [Cloudera]ImpalaJDBCDriver ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:AnalysisException: Syntax error in line 1: ... VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRI...
There is any way to alter the databasechangeloglock configuration?