Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support to disable fast-check #5917

Closed
wants to merge 1 commit into from
Closed

Add support to disable fast-check #5917

wants to merge 1 commit into from

Conversation

MalloD12
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Fixes #5784

Things to be aware of

Things to worry about

Additional Context

@@ -67,6 +69,10 @@ public class Liquibase implements AutoCloseable {
private final DefaultChangeExecListener defaultChangeExecListener = new DefaultChangeExecListener();
private final Map<String, Boolean> upToDateFastCheck = new HashMap<>();

@Getter
@Setter
private Boolean fast_check_disabled = Boolean.FALSE;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider using positive - fastCheckEnabled to make it easier to understand if it is enabled or disabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I can rename it if we want to move forward with this PR. I thought calling it this way (fast_check_disabled) because by default this configuration would stay active, but yes I'm fine renaming it.

@@ -254,6 +254,7 @@ public void afterPropertiesSet() throws LiquibaseException {
final Connection c = getDataSource().getConnection();
liquibase = createLiquibase(c);
generateRollbackFile(liquibase);
liquibase.setFast_check_disabled(Boolean.TRUE);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we change the default? This might cause a small performance hit, right?

@MalloD12 MalloD12 closed this May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

AbstractUpdateCommandStep.upToDateFastCheck global cache does not detect DB recreation
2 participants