[ https://issues.apache.org/jira/browse/MINIFI-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253901#comment-15253901
]
ASF GitHub Bot commented on MINIFI-17:
--------------------------------------
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/15#discussion_r60736740
--- Diff: minifi-assembly/pom.xml ---
@@ -261,7 +261,7 @@ limitations under the License.
<!-- nifi.properties: web properties -->
<nifi.web.war.directory>./lib</nifi.web.war.directory>
<nifi.web.http.host />
- <nifi.web.http.port>8080</nifi.web.http.port>
--- End diff --
Should be converted back to the typical 8080 default.
> Provide error handling of invalid configurations on configuration reloads
> -------------------------------------------------------------------------
>
> Key: MINIFI-17
> URL: https://issues.apache.org/jira/browse/MINIFI-17
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Reporter: Aldrin Piri
> Assignee: Joseph Percivall
>
> There should be additional facilities to provide for the case where a transformed configuration
is not valid or leads to issues with restarting.
> One approach might be to cache the last good configuration and attempt a restart, where
if the process failed to work successfully, rollback.
> Another would be to attempt some validation of the resultant flow before killing the
existing item running, but could be difficult given how closely a FlowController is tied to
runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|