creating schema with CommandLineRunner spring boot

Question

In my Spring Boot application, I'm using CommandLineRunner to create a new schema and them import some test data after that.

@Profile("create-schema")
@Component
public class CreateSchema {
    // creating schema inside. This works because I can see from the database
}

@Profile("import-data")
@Component
public class DataImporter {
}

and this is the sequence in application.properties

spring.profiles.active=${SPRING_PROFILE}, create-schema, import-data

And using this in application.properties

spring.jpa.properties.hibernate.default_schema=simba

Schema creation starts after the application has started; and after schema is created, import-data starts.

when import-data is running, I get an error that

relation schema_name.table_name does not exist

However, once the schema is created and I run the application again - it works. So, when I have to deploy my app where every time I have to create a schema to run some integration tests - it would fail there.

am I running something in wrong order?

no specific reason, I was following an article for CommandLineRunner and saw there. Is that an issue?\ — nirvair, Feb 08 '19 at 10:56
@AndrewTobilko one of the reasons mentioned there was - to separate the command line runner on different environments. on production, you may not want to import-data. — nirvair, Feb 08 '19 at 10:58
Also, why use Spring for that and not use a tool built for the job: https://flywaydb.org/ — Sofo Gial, Feb 08 '19 at 10:59
@nirvair I just feel like you are misusing them. You could make these beans conditional based on another application property. https://stackoverflow.com/questions/39857804/can-we-declare-spring-bean-conditionally — Andrew Tobilko, Feb 08 '19 at 11:06
@AndrewTobilko But, even if I do that - the command line runner will behave the same way, right? — nirvair, Feb 08 '19 at 11:09
@nirvair I don't know if a `CommandLineRunner` is the right place to do such things. First, make sure the order of beans is the same as you are expecting. Can `DataImporter` be executed before `CreateSchema`? — Andrew Tobilko, Feb 08 '19 at 11:43
No, schema is created first and then DataImporter is executed. — nirvair, Feb 08 '19 at 11:44

score 1 · Answer 1 · answered Feb 08 '19 at 12:41

Profiles are completely irrelevant here. You can ensure the schema is created before the data import by doing something like the following:

@Component("schemaCreator")
public class SchemaCreator {

    @PostConstruct
    public void initSchema(){

    }
}

Data Importer can be made dependent on the schema being initialised via the @DependsOn annotation.

https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/DependsOn.html

Beans on which the current bean depends. Any beans specified are guaranteed to be created by the container before this bean. Used infrequently in cases where a bean does not explicitly depend on another through properties or constructor arguments, but rather depends on the side effects of another bean's initialization.

@DependsOn("schemaCreator")
@Component
public class DataImporter {

    @PostConstruct
    public void initData(){

    }
}

creating schema with CommandLineRunner spring boot

1 Answers1