[
https://issues.apache.org/jira/browse/NIFI-14269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933338#comment-17933338
]
Matt Gilman commented on NIFI-14269:
------------------------------------
[~wpkinzel] Thanks for reporting this issue. I was hoping you might be able to
provide some more details or steps to reproduce. I've just verified the ability
to add/update/delete a Parameter from an existing Parameter Context and I'm not
seeing any issue locally. I tried this both standalone and in a cluster. One
interesting note from the stack trace above is that the clientId in the
Revision object is null. I can see the clientId populated in the requests.
Would you be able to provide additional steps to reproduce or possibly look at
the Network traffic in your browsers DevTools. The API for updating a Parameter
Context is asynchronous so there are a few requests we'd want to look at. The
initial request to update calls
{{/nifi-api/parameter-contexts/{pc-id}/update-requests}} and then polls an API
for the update request until it completes. I'd be interested to see if the call
is missing the clientId and I'd be interested in seeing if there is an error or
failure to update reported in the response payload that the UI isn't showing.
> Parameter Context - Cannot delete parameter from existing context
> -----------------------------------------------------------------
>
> Key: NIFI-14269
> URL: https://issues.apache.org/jira/browse/NIFI-14269
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 2.1.0
> Reporter: Bill Kinzel
> Priority: Major
>
> After upgrading from 2.0...the parameter context sync via database provider
> is buggy, causing corruption. Rows deleted from the table are not being
> deleted from the Parameter context. New values are not always updating
> either. There is no UI error, just the stack trace below...version issue of
> some type. I quickly upgraded to 2.2 to test if issue still exists...it
> does. Below 2.1 this functionality was fine.
> ----------------------
> 2025-02-16 19:11:56,329 INFO [Checkpoint FlowFile Repository]
> o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile
> Repository
> 2025-02-16 19:11:56,329 INFO [Checkpoint FlowFile Repository]
> o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile
> Repository with 197 records in 0 milliseconds
> 2025-02-16 19:11:57,438 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Stopping 0 stateless process groups
> in order to update Parameter Context
> 2025-02-16 19:11:57,438 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Stopping 0 processors in order to
> update Parameter Context
> 2025-02-16 19:11:57,438 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Disabling 0 Controller Services in
> order to update Parameter Context
> 2025-02-16 19:11:57,438 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Updating Parameter Context with ID
> 018d1b6a-ca40-11cd-b306-8a2a3bec280d
> 2025-02-16 19:11:57,447 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Successfully updated Parameter
> Context with ID 018d1b6a-ca40-11cd-b306-8a2a3bec280d
> 2025-02-16 19:11:57,447 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Updating Parameter Context with ID
> 73042277-440e-1d3c-ee9d-d1f2bbaab86b
> 2025-02-16 19:11:57,462 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Re-Enabling 0 Controller Services
> after having updated Parameter Context
> 2025-02-16 19:11:57,462 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Restarting 0 processors after having
> updated Parameter Context
> 2025-02-16 19:11:57,462 INFO [Parameter Provider Apply Thread-1]
> o.a.nifi.web.util.ParameterUpdateManager Restarting 0 stateless process
> groups after having updated Parameter Context
> 2025-02-16 19:11:57,462 ERROR [Parameter Provider Apply Thread-1]
> o.a.n.web.api.ParameterProviderResource Failed to apply parameters
> org.apache.nifi.web.InvalidRevisionException: Invalid Revision given for
> component with ID [018d1b4a-ca40-11cd-4ec2-aad7c73e9634]. Current Revision:
> [3, null, 018d1b4a-ca40-11cd-4ec2-aad7c73e9634] Proposed Revision: [2, null,
> 018d1b4a-ca40-11cd-4ec2-aad7c73e9634]
> at
> org.apache.nifi.web.revision.NaiveRevisionManager.updateRevision(NaiveRevisionManager.java:122)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.updateComponent(StandardNiFiServiceFacade.java:1147)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.updateParameterContext(StandardNiFiServiceFacade.java:1309)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:359)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
> at
> org.apache.nifi.web.NiFiServiceFacadeLock.proceedWithWriteLock(NiFiServiceFacadeLock.java:179)
> at
> org.apache.nifi.web.NiFiServiceFacadeLock.updateLock(NiFiServiceFacadeLock.java:66)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:638)
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:628)
> at
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:71)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:727)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade$$SpringCGLIB$$0.updateParameterContext(<generated>)
> at
> org.apache.nifi.web.util.ParameterUpdateManager.performParameterContextUpdate(ParameterUpdateManager.java:227)
> at
> org.apache.nifi.web.util.ParameterUpdateManager.updateParameterContexts(ParameterUpdateManager.java:172)
> at
> org.apache.nifi.web.api.ParameterProviderResource.lambda$submitApplyRequest$45(ParameterProviderResource.java:1544)
> at
> org.apache.nifi.web.api.concurrent.AsyncRequestManager$2.run(AsyncRequestManager.java:119)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> at java.base/java.lang.Thread.run(Thread.java:1583)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
