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

Aldrin Piri commented on NIFI-45:
---------------------------------

Was able to recreate using the guidance provided by Matt with a PostHTTP 
instance using an HTTPS URL in conjunction with a backing SSLContextService.

Verified the corrected response which points more directly to a cause and a 
nice improvement over the prior.

Build, tests, contrib all good: 
https://travis-ci.org/apiri/incubator-nifi/builds/104378227

+1 and will merge my local review branch into master.  Thanks for fixing this 
up.

> Bad error message on validation when controller service is invalid
> ------------------------------------------------------------------
>
>                 Key: NIFI-45
>                 URL: https://issues.apache.org/jira/browse/NIFI-45
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>            Priority: Minor
>             Fix For: 0.5.0
>
>         Attachments: 0001-NIFI-45.patch
>
>
> We have a Processor that references a Controller Service (A), and A then 
> references another Controller Service (B). The property value in A had a typo 
> that caused it to reference an invalid service identifier. The error message 
> read something along the lines of:
> 'XX' validated against 'YY' is invalid because: Controller Service is not 
> valid. No controller service exists with this ID
> This looks like 'YY' (referencing Controller Service A) was an invalid 
> identifier, but in reality Controller Service A was referencing an invalid 
> identifier.
> Proposed fix: PropertyDescriptor, when validating a Controller Service and 
> determining Controller Service is invalid should provide as its explanation
> "Controller Service is not valid: " + result
> instead of
> "Controller Service is not valid: " + result.getExplanation()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to