lordgamez opened a new pull request #1143:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1143


   Previously when parsing a single property value failed due to the failure of 
a custom validator there was only a generic error message:
   ```
   [2021-03-02 16:35:37.377] 
[org::apache::nifi::minifi::core::YamlConfiguration] [error] Invalid yaml 
configuration file
   [2021-03-02 16:35:37.377] [main] [error] Failed to load configuration due to 
exception: General Operation: Cannot convert invalid value
   ```
   The message did not indicate which property had an invalid value, which made 
it hard for the user to find the source of the failure. With this change the 
property name is logged in case of validator failure to pinpoint the source of 
the problem:
   ```
   [2021-07-26 16:53:31.190] 
[org::apache::nifi::minifi::core::YamlConfiguration] [error] Invalid value was 
set for property 'Max Poll Time'
   [2021-07-26 16:53:31.190] 
[org::apache::nifi::minifi::core::YamlConfiguration] [error] Invalid yaml 
configuration file
   [2021-07-26 16:53:31.190] [main] [error] Failed to load configuration due to 
exception: General Operation: Cannot convert invalid value
   ```
   
   https://issues.apache.org/jira/browse/MINIFICPP-1522
   
   --------------------------------------------------------------------
   Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced
        in the commit message?
   
   - [ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
   
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically main)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   ### For code changes:
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the LICENSE file?
   - [ ] If applicable, have you updated the NOTICE file?
   
   ### For documentation related changes:
   - [ ] Have you ensured that format looks appropriate for the output in which 
it is rendered?
   
   ### Note:
   Please ensure that once the PR is submitted, you check GitHub Actions CI 
results for build issues and submit an update to your PR as soon as possible.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to