ijokarumawak commented on issue #3401: NIFI-6160 NIFI-6170 Apply config error handling convention URL: https://github.com/apache/nifi/pull/3401#issuecomment-481972484 @andrewmlim Thanks for testing. To test ControllerService and Label, I used a secured environment, and remove the user's WRITE permission for the component after the user opened the configuration dialog, but before clicking "APPLY" button. That receives 403 response, and I was able to confirm the dialog still remains open. I couldn't test 400 (bad request) case with these components, too. But I'm confident that it should work if that happened, because the same implementation is confirmed to work by ReportingTask or Processor configuration dialog. And the difference between 400 and 403 is only that with 400, we do some error message string parsing to show lines as a error message list using `<li>` html markup. For the not user-friendly error message when a value outside of valid Integer range, please file another JIRA. We should fix that separately. The exception happens before NiFi REST API layer is executed. That happened when Jetty converts the requested JSON into DTO object which NiFi REST API implementation expects. I don't have any idea where/how to implement error handling logic for such exception at the moment.. The issue happens with other inputs such as Connection `Back Pressure Object Threshold`. Any inputs whose associated DTO field is a number type that has min and max limit. Int, Long ... etc.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
