Skip to content

NIFI-15452 - FlowRegistryClient validation not triggered when properties change at runtime#10757

Merged
exceptionfactory merged 1 commit intoapache:mainfrom
pvillard31:NIFI-15452
Jan 12, 2026
Merged

NIFI-15452 - FlowRegistryClient validation not triggered when properties change at runtime#10757
exceptionfactory merged 1 commit intoapache:mainfrom
pvillard31:NIFI-15452

Conversation

@pvillard31
Copy link
Contributor

Summary

NIFI-15452 - FlowRegistryClient validation not triggered when properties change at runtime

(the change is consistent with what we already have on parameter providers for example)

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
  • Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using ./mvnw clean install -P contrib-check
    • JDK 21
    • JDK 25

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

Copy link

@sfc-gh-bbende sfc-gh-bbende left a comment

Choose a reason for hiding this comment

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

+1 Looks good

@Override
public boolean isValidationNecessary() {
return getValidationStatus() != ValidationStatus.VALID;
return true;

Choose a reason for hiding this comment

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

Removed validation check and returning true by Default now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is not about returning that validation is true and we don't check anything, this is about saying that we should always check for the component's validity. Similar to parameter providers, registry clients cannot be enabled/disabled so we should always check for the validity.

Copy link
Contributor

@exceptionfactory exceptionfactory left a comment

Choose a reason for hiding this comment

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

Thanks @pvillard31, looks good, and makes sense given the lifecycle of Flow Registry Clients.

@exceptionfactory exceptionfactory merged commit c2604cb into apache:main Jan 12, 2026
14 of 17 checks passed
mark-bathori pushed a commit to mark-bathori/nifi that referenced this pull request Feb 5, 2026
…idation (apache#10757)

Signed-off-by: David Handermann <exceptionfactory@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments