Solucionado (ver solução)
Solucionado
(ver solução)
4
respostas

Erro depois de cancelar uma migration

Referente ao curso Spring Boot 3: desenvolva uma API Rest em Java

por Rodrigo Campos De Jesus
| 110.3k xp | 59 posts

Bom dia galera! Eu havia criado as outras classe para pacientes, deletei uma migration de alteração do telefone par pacientes, e agora quando fui testar a Exclusão lógica continuando dando erro em relação a migration que cancelei:

rror starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. 2023-06-12T09:45:42.389-03:00 ERROR 1628 --- [ restartedMain] o.s.boot.SpringApplication : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Validate failed: Migrations have failed validation Detected failed migration to version 4 (alter-table-pacientes-add-column-telefone). Please remove any half-completed changes then run repair to fix the schema history. Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1770) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:598) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:326) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:324) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:313) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1156) ~[spring-context-6.0.9.jar:6.0.9] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:931) ~[spring-context-6.0.9.jar:6.0.9] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:608) ~[spring-context-6.0.9.jar:6.0.9] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.1.0.jar:3.1.0] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:733) ~[spring-boot-3.1.0.jar:3.1.0] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:435) ~[spring-boot-3.1.0.jar:3.1.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:311) ~[spring-boot-3.1.0.jar:3.1.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1305) ~[spring-boot-3.1.0.jar:3.1.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1294) ~[spring-boot-3.1.0.jar:3.1.0] at med.voll.api.ApiApplication.main(ApiApplication.java:10) ~[classes/:na] at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[na:na] at java.base/java.lang.reflect.Method.invoke(Method.java:578) ~[na:na] at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49) ~[spring-boot-devtools-3.1.0.jar:3.1.0] Caused by: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation Detected failed migration to version 4 (alter-table-pacientes-add-column-telefone). Please remove any half-completed changes then run repair to fix the schema history. Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE

Essas são as migrations atuais:

Insira aqui a descrição dessa imagem para ajudar na acessibilidade

4 respostas
por Rodrigo da Silva Ferreira Caneppele
| 4512k xp | 7763 posts
Instrutor Instrutor

Oi Rodrigo!

As migrations são imutáveis! Uma vez que elas executaram você não pode mexer nelas (alterar o código sql, renomear o arquiivo, etc). Agora você vai precisar apagar da tabela do flyway as migrations que ele falhou em executar.

por Rodrigo Campos De Jesus
| 110.3k xp | 59 posts

COnsegui resoover aquele erro com essa query :

delete from flyway_schema_history where success = 0;

mas agora depois que renomemei algumas migrations está dando esse erro:

Migration checksum mismatch for migration version 3 -> Applied to database : 956260868 -> Resolved locally : 1410818282 Either revert the changes to the migration, or run repair to update the schema history. Migration checksum mismatch for migration version 4 -> Applied to database : 1410818282 -> Resolved locally : -613902525 Either revert the changes to the migration, or run repair to update the schema history. Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE 2023-06-12T11:01:00.184-03:00 INFO 12540 --- [ restartedMain] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated... 2023-06-12T11:01:00.214-03:00 INFO 12540 --- [ restartedMain] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed. 2023-06-12T11:01:00.216-03:00 INFO 12540 --- [ restartedMain] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2023-06-12T11:01:00.233-03:00 INFO 12540 --- [ restartedMain] .s.b.a.l.ConditionEvaluationReportLogger :

Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. 2023-06-12T11:01:00.254-03:00 ERROR 12540 --- [ restartedMain] o.s.boot.SpringApplication : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Validate failed: Migrations have failed validation Migration checksum mismatch for migration version 3 -> Applied to database : 956260868 -> Resolved locally : 1410818282 Either revert the changes to the migration, or run repair to update the schema history. Migration checksum mismatch for migration version 4 -> Applied to database : 1410818282 -> Resolved locally : -613902525 Either revert the changes to the migration, or run repair to update the schema history. Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1770) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:598) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:326) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-6.0.9.jar:6.0.9] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:324) ~[spring-beans-6.0.9.jar:6.0.9]

por Rodrigo da Silva Ferreira Caneppele
| 4512k xp | 7763 posts
Instrutor Instrutor

Então, foi justamente o que eu disse na mensagem anterior, você não pode renomear as migrations que já foram executadas. O Flyway vai detectar e causar um erro na aplicação.

Agora você vai precisar apagar todas as migrations: delete from flyway_schema_history, mas vai precisar também apagar as outras tabelas, pois quando o flyway for executar novamente as migrations vai tentar criar tabelas e não conseguir, pois elas já existem no banco.

Ou seja, o melhor a fazer e apagar o banco e criar novamente:

drop database vollmed_api;
create database vollmed_api;
solução!
por Rodrigo Campos De Jesus
| 110.3k xp | 59 posts

Obrigado Rodrigo! Deu certo!!!!!!

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software