Camunda Update with Camunda provided Liquibase scripts

Camunda 7 Topics Discussion & Questions
1

Hey Folks,

I just tried the Camunda 7.17 Update with Liquibase inside our project liquibase changelog and run into the following problem. D:

Our Setup:

  • Camunda in Spring Boot
  • Using Liquibase inside the project development (adding database tables)

The project changelog (resources/db/db.changelog-master.xml) looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
    xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
   http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd">

    <property name="databaseType" value="h2" dbms="h2"/>
    <property name="databaseType" value="postgresql" dbms="postgresql"/>

    <include file="org/camunda/bpm/engine/db/liquibase/camunda-changelog.xml" />
    <!-- cusotom scripts -->
</databaseChangeLog>

So far it would work with 7.16 scripts, but with 7.17 the first update is inside the camunda-changelog.xml and liquibase can not resolve the relative path.

Error message:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LiquibaseException: liquibase.exception.UnexpectedLiquibaseException: 
java.io.IOException: The file ../upgrade/h2_engine_7.16_to_7.17.sql was not found in
    - Spring resources
Specifying files by absolute path was removed in Liquibase 4.0. Please use a relative path or add '/' to the classpath parameter.

Is there a right approach to implement the camunda-changelog.xml?

I’m thankful for any Ideas

Cheers
Jan

2

Hi @JanvN,

Unfortunately liquibase can’t load the relative paths with parent directory navigation from the jar. While it’s probably a bug in liquibase itself we already have a bug ticket to fix this in our changelog file.

Until it’s not fixed you can only solve it with workarounds. One would be to copy the camunda db files from the jar into the resources of your project and include a link to that camunda-changelog.xml.

I hope this helps.

–
Daniel

2 Likes
3

Thanks for the quick reply. We will add imports for required scripts.

4

@JanvN I am trying to do the same thing as you did by including engine migration file in my own db.changelog-master.xml in spring boot application.

<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
                      http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.6.xsd">
    <include context="default" file="classpath:/org/camunda/bpm/engine/db/liquibase/camunda-changelog.xml"/>
<!-- custom scripts -->
    <include context="default" file="changelog/CORE-2263-add-operation-result-column.changelog.xml"/>
</databaseChangeLog>

When application starts, migration fails because of existing tables from engine. It means that the change location does not apply spring.liquibase.change-log: classpath:changelog/db.changelog-master.xml to engines changelog. How did you solve this issue if you had it?
Thank you

5

Hello @Saeed_Ansari,

sorry for the late reply. No we didn’t solved it. We added create and update files referencing the Camunda files. In this way you still need du check if updates have scripts.
Please check if Camunda 7.18, 7.17.3, 7.16.10 or 7.18.0-alpha3 have any changes, since this are mentioned as fix versions in the bug ticket.

Cheers Jan

6

Hi @JanvN
Thank you for your response. Problem with relative path is solved in version 7.18, but my issue now is that engine starts before liquibase executes scripts and consequently engine fails because it cannot find tables needed.
With camunda.bpm.database.schema-update: false and having the same master changelog as yours.
I am wondering if you had the same issue? What I need to do is to execute liquibase files before engine starts.

Thank you,
Saeed