[ https://issues.apache.org/jira/browse/NIFI-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311659#comment-16311659 ]
ASF GitHub Bot commented on NIFI-4733: -------------------------------------- Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/2370#discussion_r159703442 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/ProcessGroupResource.java --- @@ -620,13 +623,13 @@ public Response updateVariableRegistry( public Response submitUpdateVariableRegistryRequest( @Context final HttpServletRequest httpServletRequest, @ApiParam(value = "The process group id.", required = true) @PathParam("id") final String groupId, - @ApiParam(value = "The process group configuration details.", required = true) final VariableRegistryEntity requestEntity) { + @ApiParam(value = "The process group configuration details.", required = true) final VariableRegistryEntity requestVariableRegistryEntity) { --- End diff -- Probably here too, then. > Issue with variable registry two phase commit > --------------------------------------------- > > Key: NIFI-4733 > URL: https://issues.apache.org/jira/browse/NIFI-4733 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.4.0 > Reporter: Matt Gilman > Assignee: Matt Gilman > > Need to address the logic issue during the two-phase commit exchange when > running clustered and invoking a variable registry update request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)