Skip to content

NIFI-16070: Add nifi-api support for migrateProperties to Connectors.#102

Merged
markap14 merged 1 commit into
apache:mainfrom
bobpaulin:NIFI-16070
Jul 6, 2026
Merged

NIFI-16070: Add nifi-api support for migrateProperties to Connectors.#102
markap14 merged 1 commit into
apache:mainfrom
bobpaulin:NIFI-16070

Conversation

@bobpaulin

@bobpaulin bobpaulin commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Summary

NIFI-16070

API changes to support https://issues.apache.org/jira/browse/NIP-34

Add migrateProperties API to Connector

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 Formatting

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

@markap14 markap14 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @bobpaulin I think this makes sense. I did call out the hasStep/hasProperty - let me know what you think, if there's a strong reason for it or if it makes sense to eliminate. Otherwise I'm in favor of this addition.

* @param stepName the name of the configuration step
* @return <code>true</code> if this configuration contains the given step
*/
boolean hasStep(String stepName);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is there a benefit in having this over just using getStepNames().contains(stepName)? I'd recommend keeping the interface minimal unless there's a reason for it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It is not required. As you've show there is an alternative way to do it. I was trying to stay consistent with https://github.com/apache/nifi-api/blob/main/src/main/java/org/apache/nifi/migration/PropertyConfiguration.java which has a similar redundancy.

Open to removing but I think there is some benefit from providing a consistent approach with Processors and Controller Services.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ah. Yeah, that's fair.

* @param propertyName the property name
* @return <code>true</code> if this step has an entry for the property, including when its value reference is null
*/
boolean hasProperty(String propertyName);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Similar to hasStep, I'd recommend omitting if there's not a strong reason for having.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Similar to above. I was trying to stay consistent with https://github.com/apache/nifi-api/blob/main/src/main/java/org/apache/nifi/migration/PropertyConfiguration.java which has a similar redundancy.

@bobpaulin bobpaulin marked this pull request as ready for review July 6, 2026 13:46
@markap14 markap14 merged commit 9d6c8ba into apache:main Jul 6, 2026
1 check passed
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