Tatiana Fernández

Hi @amazing4u and @samuelm00. The error message problem is fixed with #5828 - could you use the artifacts from that PR to show what the error is? Let us know...

@samuelm00 a [fix to this](https://github.com/liquibase/liquibase/pull/5828) was merged to master last week. Could you use this updated version to re-test and let us know if the error message contains more information?

@amazing4u You can download it from here: https://github.com/liquibase/liquibase/actions/runs/8930022026/artifacts/1468641178 or obtain it using GPM [(gradle](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry#using-a-published-package) or [maven](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) ): ``` org.liquibase liquibase-core master-SNAPSHOT ``` ``` api("org.liquibase:liquibase-core:master-SNAPSHOT") ```

@amazing4u no worries, thank you for trying. I can confirm that the problem is solved with the current master version (as of 15/05/2024). To reproduce this scenario: have an entity...

Hi @doakd, thank you for reporting this issue. I've tested this using Liquibase version 4.26.0, liquibase-databricks versions 1.1.2 and 1.1.3, using the changeset you've provided. In my case, the changeset...

@doakd thank you for providing more info. I still can't replicate what you're reporting, but it's known that Liquibase extensions can sometimes get in the way of executions. `liquibase-databricks` version...

@filipelautert I'm still not getting errors that block execution, but the extension is crowding the logs and taking up resources. @doakd we are currently looking into improving the way Liquibase...

@doakd I don't, so there's probably some mix of configurations or some collation in your environment that makes the liquibase-databricks extension fail. Still, it shouldn't have to matter as you're...

@doakd the issue has been addressed and will be included in the next extension release, which will be either next week or the following one. You can see the changes...

Hi @Poundex, thank you for reporting this issue. I can confirm that this is a problem, and it's most likely caused by the filepath processing - for 3.10.2, the filename...