Skip to content

NIFI-15561: Do not consider references from Ghosted components in Par…#10865

Open
markap14 wants to merge 2 commits intoapache:mainfrom
markap14:NIFI-15561
Open

NIFI-15561: Do not consider references from Ghosted components in Par…#10865
markap14 wants to merge 2 commits intoapache:mainfrom
markap14:NIFI-15561

Conversation

@markap14
Copy link
Contributor

@markap14 markap14 commented Feb 6, 2026

…ameter reference sensitivity checks

Summary

NIFI-00000

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
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 for addressing this issue and providing detailed tests for the change @markap14. Skipping the Parameter reference checks for missing extensions seems like a straightforward and reasonable change at the framework level given the totality of the impact.

I noted two minor recommendations on the test classes. The branch commits also need to be signed.


// Verify processor is VALID
getClientUtil().waitForValidProcessor(processorId);
logger.info("Processor {} is VALID with non-sensitive parameter value 'hello'", processorId);
Copy link
Contributor

Choose a reason for hiding this comment

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

Most of the system test do not have local logging, it seems like most or all of the test logging should be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed that most system tests don't have much of any logging. But I don't think I would agree that is advantageous. I've found of late that adding this type of logging can be valuable when troubleshooting because the timestamps can be easily correlated with the timestamps in the nifi-app.log, nifi-user.log, etc. making it easier to understand what happened. I also find it's helpful when running tests manually from an IDE, if things are taking a bit and especially if it gets "stuck" for some reason it makes it much more clear what's happening. So I think rather than stripping out all of the logging here we need to consider adding in more logging to the system tests going forward.

final ParameterContext context = createStandardParameterContext(referenceManager);

final ProcessorNode procNode = getProcessorNode("abc", referenceManager);
Mockito.when(procNode.isExtensionMissing()).thenReturn(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

I recommend replacing the qualified Mockito.when and Mockito.mock() references with static imports.

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.

2 participants