conductor-oss/conductor

[BUG] flyway.postgresql.transactional.lock didn't find in flyway

Open

#123 opened on Apr 9, 2024

View on GitHub
 (5 comments) (2 reactions) (1 assignee)Java (894 forks)batch import
bughelp wantedquestion

Repository metrics

Stars
 (31,816 stars)
PR merge metrics
 (Avg merge 7d 14h) (34 merged PRs in 30d)

Description

Describe the bug After getting a new version of conductor, I've got an error while spring boot app is starting.

As far as I researched, flyway does not find prop flyway.postgresql.transactional.lock

Details Conductor version: implementation "org.conductoross:conductor-common:3.18.0" implementation "org.conductoross:conductor-postgres-persistence:3.18.0" implementation "org.conductoross:conductor-core:3.18.0" implementation "org.conductoross:conductor-rest:3.18.0"

To Reproduce Steps to reproduce the behavior:

  1. start Spring boot app
  2. See error in logs: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayForPrimaryDb' defined in class path resource [com/netflix/conductor/postgres/config/PostgresConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.flywaydb.core.Flyway]: Factory method 'flywayForPrimaryDb' threw exception; nested exception is org.flywaydb.core.api.FlywayException: Unknown configuration property: flyway.postgresql.transactional.lock

Expected behavior Spring boot app with conductor runs as expected

Contributor guide

Research direction
Examine the PostgresConfiguration class (mentioned in the stack trace) to see how Flyway is configured. Check the Flyway version used by conductor 3.18.0 and verify if the property `flyway.postgresql.transactional.lock` is valid. Review the issue comments for any suggested fixes or version compatibility notes.
Tech stack
javaspringpostgresqlsql
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaSpring BootFlywayPostgreSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70