Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Better error message (on yaml parse error?) / java.lang.NullPointerException
Description
while running an update, i received the following error, which i suspect should be caught, then rethrown as something more helpful:
broken yaml to trigger this (accidently added 'loadUpdateData' instead of replacing 'loadData'):
changeSet: id: LoadSeed-FlagState author: me changes:
loadUpdateData:
loadData: tableName: ... primaryKey: Name
environment is the docker container rubms/liquibase-mssql:6.2.2 (customer-db-release_1 is messages from the docker component that was running liquibase)
customer-db-release_1 | Unexpected error running Liquibase: Unknown Reason customer-db-release_1 | customer-db-release_1 | SEVERE 7/27/18 3:08 AM: liquibase: seeds/ref/changelog.yaml::LoadSeed-FlagState::Andrew Hill: Unknown Reason customer-db-release_1 | java.lang.NullPointerException customer-db-release_1 | at java.io.File.<init>(File.java:277) customer-db-release_1 | at liquibase.resource.FileSystemResourceAccessor.getResourcesAsStream(FileSystemResourceAccessor.java:68) customer-db-release_1 | at liquibase.resource.CompositeResourceAccessor.getResourcesAsStream(CompositeResourceAccessor.java:28) customer-db-release_1 | at liquibase.util.StreamUtil.singleInputStream(StreamUtil.java:186) customer-db-release_1 | at liquibase.util.StreamUtil.openFromClasspath(StreamUtil.java:240) customer-db-release_1 | at liquibase.util.StreamUtil.openStream(StreamUtil.java:151) customer-db-release_1 | at liquibase.change.core.LoadDataChange.generateCheckSum(LoadDataChange.java:467) customer-db-release_1 | at liquibase.changelog.ChangeSet.generateCheckSum(ChangeSet.java:251) customer-db-release_1 | at liquibase.changelog.ChangeSet.toString(ChangeSet.java:770) customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.createKey(ChangeLogIterator.java:107) customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.alreadySaw(ChangeLogIterator.java:115) customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:78) customer-db-release_1 | at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:259) customer-db-release_1 | at liquibase.Liquibase.update(Liquibase.java:210) customer-db-release_1 | at liquibase.Liquibase.update(Liquibase.java:192) customer-db-release_1 | at liquibase.integration.commandline.Main.doMigration(Main.java:1130) customer-db-release_1 | at liquibase.integration.commandline.Main.run(Main.java:188) customer-db-release_1 | at liquibase.integration.commandline.Main.main(Main.java:103)
while running an update, i received the following error, which i suspect should be caught, then rethrown as something more helpful:
broken yaml to trigger this (accidently added 'loadUpdateData' instead of replacing 'loadData'):
changeSet:
id: LoadSeed-FlagState
author: me
changes:
loadUpdateData:
loadData:
tableName: ...
primaryKey: Name
environment is the docker container rubms/liquibase-mssql:6.2.2
(customer-db-release_1 is messages from the docker component that was running liquibase)
customer-db-release_1 | Unexpected error running Liquibase: Unknown Reason
customer-db-release_1 |
customer-db-release_1 | SEVERE 7/27/18 3:08 AM: liquibase: seeds/ref/changelog.yaml::LoadSeed-FlagState::Andrew Hill: Unknown Reason
customer-db-release_1 | java.lang.NullPointerException
customer-db-release_1 | at java.io.File.<init>(File.java:277)
customer-db-release_1 | at liquibase.resource.FileSystemResourceAccessor.getResourcesAsStream(FileSystemResourceAccessor.java:68)
customer-db-release_1 | at liquibase.resource.CompositeResourceAccessor.getResourcesAsStream(CompositeResourceAccessor.java:28)
customer-db-release_1 | at liquibase.util.StreamUtil.singleInputStream(StreamUtil.java:186)
customer-db-release_1 | at liquibase.util.StreamUtil.openFromClasspath(StreamUtil.java:240)
customer-db-release_1 | at liquibase.util.StreamUtil.openStream(StreamUtil.java:151)
customer-db-release_1 | at liquibase.change.core.LoadDataChange.generateCheckSum(LoadDataChange.java:467)
customer-db-release_1 | at liquibase.changelog.ChangeSet.generateCheckSum(ChangeSet.java:251)
customer-db-release_1 | at liquibase.changelog.ChangeSet.toString(ChangeSet.java:770)
customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.createKey(ChangeLogIterator.java:107)
customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.alreadySaw(ChangeLogIterator.java:115)
customer-db-release_1 | at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:78)
customer-db-release_1 | at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:259)
customer-db-release_1 | at liquibase.Liquibase.update(Liquibase.java:210)
customer-db-release_1 | at liquibase.Liquibase.update(Liquibase.java:192)
customer-db-release_1 | at liquibase.integration.commandline.Main.doMigration(Main.java:1130)
customer-db-release_1 | at liquibase.integration.commandline.Main.run(Main.java:188)
customer-db-release_1 | at liquibase.integration.commandline.Main.main(Main.java:103)