[ 
https://issues.apache.org/jira/browse/NIP-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950119#comment-17950119
 ] 

Matt Burgess commented on NIP-1:
--------------------------------

I'd like to revisit this and get it out for a vote. According to the NIP 
process it shouldn't need commitment for the work, otherwise only engineers 
would really be able to submit a NIP. NIP-5 was approved and the PR for the 
nifi-api changes was submitted and merged without commitment for the 
implementation work, I'd like to do the same for this one. Thoughts?

> Add VerifiableRegistryClient interface to verify Registry Client 
> implementations
> --------------------------------------------------------------------------------
>
>                 Key: NIP-1
>                 URL: https://issues.apache.org/jira/browse/NIP-1
>             Project: NiFi Improvement Proposal
>          Issue Type: New Feature
>            Reporter: Matt Burgess
>            Priority: Normal
>              Labels: nifi-api, nifi-registry
>
> Motivation
> To verify basic connectivity from a NiFiRegistryClient to a Registry instance
> Scope
> Add VerifiableRegistryClient interface to verify NiFiRegistryClient 
> implementations
>  
> Compatibility
> Existing implementations in Apache NiFi will need to implement the verify() 
> method, but a default no-op implementation will be offered so as not to 
> interrupt compatibility. The no-op implementation should log/report that no 
> actual verification was applied.
> Description
> Registry Clients didn't exist when the Verifiable (ControllerService, 
> Processor, ReportingTask, ParameterProvider, etc.) interfaces were added.
> Verification
> Implement the verify method for JerseyNiFiRegistryClient (contributed as a 
> separate Jira) and run with a live instance, validating that incorrect 
> configurations return error message(s) and a correct configuration returns 
> success. Fetching the available buckets should suffice for verification, 
> whether buckets exist or not.
> Alternatives
> None identified, current behavior does not allow verification of 
> NiFiRegistryClient instances



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to