You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting below exception when trying to run the jar created by using maven-shade plugin. In Intellij the liquibase update operation executes fine when i run my main class.
using 4.3.5 in maven pom.xml for both core and teradata extension.
Using below line of code to instantiate liquibase:
Database database = DatabaseFactory.getInstance().findCorrectDatabaseImplementation(new JdbcConnection(conn));
Liquibase liquibase = new Liquibase(changeLogPath, new ClassLoaderResourceAccessor(), new JdbcConnection(conn));
the first line throws below exception
Exception : Cannot find generators for database class liquibase.ext.teradata.database.TeradataDatabase, statement: SELECT DATABASE
java.lang.IllegalStateException: Cannot find generators for database class liquibase.ext.teradata.database.TeradataDatabase, statement: SELECT DATABASE
at liquibase.sqlgenerator.SqlGeneratorFactory.generateSql(SqlGeneratorFactory.java:218)
at liquibase.executor.AbstractExecutor.applyVisitors(AbstractExecutor.java:105)
at liquibase.executor.jvm.JdbcExecutor.access$600(JdbcExecutor.java:40)
at liquibase.executor.jvm.JdbcExecutor$QueryStatementCallback.doInStatement(JdbcExecutor.java:454)
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:82)
at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:168)
at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:176)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:184)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:199)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:194)
at liquibase.ext.teradata.database.TeradataDatabase.getDatabaseName(TeradataDatabase.java:42)
at liquibase.ext.teradata.database.TeradataDatabase.getDefaultCatalogName(TeradataDatabase.java:106)
at liquibase.changelog.ChangeLogParameters.(ChangeLogParameters.java:60)
at liquibase.Liquibase.(Liquibase.java:123)
Getting below exception when trying to run the jar created by using maven-shade plugin. In Intellij the liquibase update operation executes fine when i run my main class.
using 4.3.5 in maven pom.xml for both core and teradata extension.
Using below line of code to instantiate liquibase:
Database database = DatabaseFactory.getInstance().findCorrectDatabaseImplementation(new JdbcConnection(conn));
Liquibase liquibase = new Liquibase(changeLogPath, new ClassLoaderResourceAccessor(), new JdbcConnection(conn));
the first line throws below exception
Exception : Cannot find generators for database class liquibase.ext.teradata.database.TeradataDatabase, statement: SELECT DATABASE
java.lang.IllegalStateException: Cannot find generators for database class liquibase.ext.teradata.database.TeradataDatabase, statement: SELECT DATABASE
at liquibase.sqlgenerator.SqlGeneratorFactory.generateSql(SqlGeneratorFactory.java:218)
at liquibase.executor.AbstractExecutor.applyVisitors(AbstractExecutor.java:105)
at liquibase.executor.jvm.JdbcExecutor.access$600(JdbcExecutor.java:40)
at liquibase.executor.jvm.JdbcExecutor$QueryStatementCallback.doInStatement(JdbcExecutor.java:454)
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:82)
at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:168)
at liquibase.executor.jvm.JdbcExecutor.query(JdbcExecutor.java:176)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:184)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:199)
at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:194)
at liquibase.ext.teradata.database.TeradataDatabase.getDatabaseName(TeradataDatabase.java:42)
at liquibase.ext.teradata.database.TeradataDatabase.getDefaultCatalogName(TeradataDatabase.java:106)
at liquibase.changelog.ChangeLogParameters.(ChangeLogParameters.java:60)
at liquibase.Liquibase.(Liquibase.java:123)
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered: