[jira] [Comment Edited] (NIFI-12738) Nifi registry ranger integration is not working
[
https://issues.apache.org/jira/browse/NIFI-12738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819098#comment-17819098
]
Pradeep Agrawal edited comment on NIFI-12738 at 2/21/24 7:07 AM:
-
>From the
>[commit|https://github.com/apache/ranger/commit/1dee2b377e20b811cc568f30ff789b50d8e241ec]
> it seems javax.ws.rs.core.Cookie class is needed from ranger end.
but seems its being excluded from Nifi end
[commit.|https://github.com/apache/nifi/commit/dfa683af0e00cd631905d45365bc797fbdce66ee]
This commit went before the above mentioned ranger commit so that could be one
reason.
was (Author: pradeep.agrawal):
>From the
>[commit|https://github.com/apache/ranger/commit/1dee2b377e20b811cc568f30ff789b50d8e241ec]
> it seems javax.ws.rs.core.Cookie class is needed from ranger end.
but seems its being excluded from Nifi end
[commit.|https://github.com/apache/nifi/commit/dfa683af0e00cd631905d45365bc797fbdce66ee]
This commit went before the above commit so that could be one reason.
> Nifi registry ranger integration is not working
> ---
>
> Key: NIFI-12738
> URL: https://issues.apache.org/jira/browse/NIFI-12738
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Registry
>Affects Versions: 2.0.0-M2, 2.0.0
>Reporter: Zoltán Kornél Török
>Priority: Critical
>
> h1. Bug description
> I want to try recently released nifi 2 m2 release in an environment,
> where we use ranger. Nifi registry ui was not able to load and I got the
> following error in the log:
> {code:java}
> Caused by:
> org.apache.nifi.registry.security.authorization.AuthorizerFactoryException:
> Failed to construct Authorizer.
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(AuthorizerFactory.java:267)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.CGLIB$getAuthorizer$4()
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$FastClass$$1.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:258)
> at
> org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.getAuthorizer()
> 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:351)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:385)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:717)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$1.getAuthorizer()
> 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.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:140)
> ... 89 common frames omitted
> Caused by:
> org.apache.nifi.registry.security.exception.SecurityProviderCreationException:
> Error creating RangerBasePlugin
> at
> org.apache.nifi.registry.ranger.RangerAuthorizer.onConfigured(RangerAuthorizer.java:178)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$ManagedAuthorizerWrapper.onConfigured(AuthorizerFactory.java:817)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(Authori
[jira] [Comment Edited] (NIFI-12738) Nifi registry ranger integration is not working
[
https://issues.apache.org/jira/browse/NIFI-12738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819098#comment-17819098
]
Pradeep Agrawal edited comment on NIFI-12738 at 2/21/24 7:06 AM:
-
>From the
>[commit|https://github.com/apache/ranger/commit/1dee2b377e20b811cc568f30ff789b50d8e241ec]
> it seems javax.ws.rs.core.Cookie class is needed from ranger end.
but seems its being excluded from Nifi end
[commit.|https://github.com/apache/nifi/commit/dfa683af0e00cd631905d45365bc797fbdce66ee]
This commit went before the above commit so that could be one reason.
was (Author: pradeep.agrawal):
>From the
>[commit|https://github.com/apache/ranger/commit/1dee2b377e20b811cc568f30ff789b50d8e241ec]
> it seems javax.ws.rs.core.Cookie class is needed from ranger end.
but its seem being excluded from Nifi end
[commit.|https://github.com/apache/nifi/commit/dfa683af0e00cd631905d45365bc797fbdce66ee]
This commit went before the above commit so that could be one reason.
> Nifi registry ranger integration is not working
> ---
>
> Key: NIFI-12738
> URL: https://issues.apache.org/jira/browse/NIFI-12738
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Registry
>Affects Versions: 2.0.0-M2, 2.0.0
>Reporter: Zoltán Kornél Török
>Priority: Critical
>
> h1. Bug description
> I want to try recently released nifi 2 m2 release in an environment,
> where we use ranger. Nifi registry ui was not able to load and I got the
> following error in the log:
> {code:java}
> Caused by:
> org.apache.nifi.registry.security.authorization.AuthorizerFactoryException:
> Failed to construct Authorizer.
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(AuthorizerFactory.java:267)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.CGLIB$getAuthorizer$4()
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$FastClass$$1.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:258)
> at
> org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.getAuthorizer()
> 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:351)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:385)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:717)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$1.getAuthorizer()
> 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.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:140)
> ... 89 common frames omitted
> Caused by:
> org.apache.nifi.registry.security.exception.SecurityProviderCreationException:
> Error creating RangerBasePlugin
> at
> org.apache.nifi.registry.ranger.RangerAuthorizer.onConfigured(RangerAuthorizer.java:178)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$ManagedAuthorizerWrapper.onConfigured(AuthorizerFactory.java:817)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(AuthorizerFactory.java:26
[jira] [Commented] (NIFI-12738) Nifi registry ranger integration is not working
[
https://issues.apache.org/jira/browse/NIFI-12738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819098#comment-17819098
]
Pradeep Agrawal commented on NIFI-12738:
>From the
>[commit|https://github.com/apache/ranger/commit/1dee2b377e20b811cc568f30ff789b50d8e241ec]
> it seems javax.ws.rs.core.Cookie class is needed from ranger end.
but its seem being excluded from Nifi end
[commit.|https://github.com/apache/nifi/commit/dfa683af0e00cd631905d45365bc797fbdce66ee]
This commit went before the above commit so that could be one reason.
> Nifi registry ranger integration is not working
> ---
>
> Key: NIFI-12738
> URL: https://issues.apache.org/jira/browse/NIFI-12738
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Registry
>Affects Versions: 2.0.0-M2, 2.0.0
>Reporter: Zoltán Kornél Török
>Priority: Critical
>
> h1. Bug description
> I want to try recently released nifi 2 m2 release in an environment,
> where we use ranger. Nifi registry ui was not able to load and I got the
> following error in the log:
> {code:java}
> Caused by:
> org.apache.nifi.registry.security.authorization.AuthorizerFactoryException:
> Failed to construct Authorizer.
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(AuthorizerFactory.java:267)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.CGLIB$getAuthorizer$4()
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$FastClass$$1.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:258)
> at
> org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$0.getAuthorizer()
> 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:351)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:385)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:765)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:717)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$$SpringCGLIB$$1.getAuthorizer()
> 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.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:140)
> ... 89 common frames omitted
> Caused by:
> org.apache.nifi.registry.security.exception.SecurityProviderCreationException:
> Error creating RangerBasePlugin
> at
> org.apache.nifi.registry.ranger.RangerAuthorizer.onConfigured(RangerAuthorizer.java:178)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory$ManagedAuthorizerWrapper.onConfigured(AuthorizerFactory.java:817)
> at
> org.apache.nifi.registry.security.authorization.AuthorizerFactory.getAuthorizer(AuthorizerFactory.java:260)
> ... 110 common frames omitted
> Caused by: java.lang.NoClassDefFoundError: javax/ws/rs/core/Cookie
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:421)
> at java.base/java.lang.Class.forName(Class.java:412)
> at
> org.apache.ranger.plugin.policyengine.RangerPluginContext.createAdminClient(RangerPluginContext.java:96)
> at
> org.apache.ranger.p
[jira] [Created] (NIFI-12828) DatabaseTableSchemaRegistry improvement to handle BIT/Boolean Type
RAVINARAYAN SINGH created NIFI-12828:
Summary: DatabaseTableSchemaRegistry improvement to handle
BIT/Boolean Type
Key: NIFI-12828
URL: https://issues.apache.org/jira/browse/NIFI-12828
Project: Apache NiFi
Issue Type: Improvement
Affects Versions: 1.25.0
Reporter: RAVINARAYAN SINGH
Assignee: RAVINARAYAN SINGH
The issue stems from the fact that for the PostgreSQL JDBC driver, the Boolean
type is mapped to {{{}java.sql.Types.BIT{}}}, not {{{}BOOLEAN{}}}. This causes
the line {{columnResultSet.getInt("DATA_TYPE")}} to return -7, which
corresponds to {{{}BIT{}}}, and
{{DataTypeUtils.getDataTypeFromSQLTypeValue(dataType)}} to return {{{}null{}}},
leading to a null pointer exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11859) Nifi in standalone mode is not able to enable EmbeddedHazelcastCacheManager
[
https://issues.apache.org/jira/browse/NIFI-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819071#comment-17819071
]
Bob Paulin commented on NIFI-11859:
---
Looks like Hazelcast will enable the Multicast Joinger[1] if autodetect is
enabled. And it is by default [2]. This causes Multicast to be enabled when
this is run locally
{code:java}
2024-02-20 19:14:41,547 INFO [Timer-Driven Process Thread-6]
com.hazelcast.instance.impl.Node [192.168.56.1]:5701 [nifi] [5.3.5] Using
Multicast discovery {code}
By disabling the auto detect this does not happen
[https://github.com/apache/nifi/pull/8440]
I get the following in the logs which I believe is expected.
{code:java}
2024-02-20 19:23:15,870 WARN [Timer-Driven Process Thread-2]
com.hazelcast.instance.impl.Node [192.168.56.1]:5701 [nifi] [5.3.5] No join
method is enabled! Starting standalone. {code}
This should also address the issue above since it appears to be hitting a
usecase where the DiscoveryJoiner is enabled. This should also be suppressed
by autodetect being disabled [3]. This appears to happen in both 1.x and 2.x
[1]
[https://github.com/hazelcast/hazelcast/blob/a3ae01dcbfa32e3b314047506dadf837d54e8e2a/hazelcast/src/main/java/com/hazelcast/instance/impl/Node.java#L946|https://github.com/hazelcast/hazelcast/blob/e3dd651a78e97c6702ce4260e6263d4818fb29b1/hazelcast/src/main/java/com/hazelcast/instance/impl/Node.java#L974]
[2]
[https://github.com/hazelcast/hazelcast/blob/e3dd651a78e97c6702ce4260e6263d4818fb29b1/hazelcast/src/main/java/com/hazelcast/config/AutoDetectionConfig.java#L28]
[3]https://github.com/hazelcast/hazelcast/blob/a3ae01dcbfa32e3b314047506dadf837d54e8e2a/hazelcast/src/main/java/com/hazelcast/instance/impl/Node.java#L938
> Nifi in standalone mode is not able to enable EmbeddedHazelcastCacheManager
>
>
> Key: NIFI-11859
> URL: https://issues.apache.org/jira/browse/NIFI-11859
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.22.0
>Reporter: Jeetendra G Vasisht
>Priority: Blocker
> Attachments: embeddedHazelcastNifiControllerservice.PNG, nifi--app.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> EmbeddedHazelcastCacheManager Controller gets enabled in cluster mode with
> "All Nodes" clustering strategy, but having issue when tried to run in
> standalone mode with "None" clustering strategy. This is observed in
> Kubernetes Environment and this is coming as part of internal Nifi packaging
> and any external dependency or code related to Hazelcast is not being used.
> Controller gets stuck in Enabling state:
> !embeddedHazelcastNifiControllerservice.PNG|width=662,height=131!
> Respective Logs have been attached
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-11859: Ensure Hazelcast can not join a network when Cluster is NONE [nifi]
bobpaulin opened a new pull request, #8440: URL: https://github.com/apache/nifi/pull/8440 # Summary [NIFI-11859](https://issues.apache.org/jira/browse/NIFI-11859) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x ] Pull Request based on current revision of the `main` branch - [ x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. Full build and created EmbeddedHazelcastCacheManager locally ### Build - [ x] Build completed using `mvn clean install -P contrib-check` - [x ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]
exceptionfactory commented on PR #8407: URL: https://github.com/apache/nifi/pull/8407#issuecomment-1955870544 Thanks for the initial feedback @markap14! Based on further discussion, I will be following up with additional changes to incorporate log level updates from Logback. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-12784) Only display 'Path Not Found Behavior' property in EvaluateJsonPath when 'Destination' property value is flowfile-attributes
[ https://issues.apache.org/jira/browse/NIFI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12784. - Fix Version/s: 2.0.0 1.26.0 Resolution: Fixed > Only display 'Path Not Found Behavior' property in EvaluateJsonPath when > 'Destination' property value is flowfile-attributes > > > Key: NIFI-12784 > URL: https://issues.apache.org/jira/browse/NIFI-12784 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Labels: backport-needed > Fix For: 2.0.0, 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently in EvaluateJsonPath the 'Path Not Found Behavior' property which > defines behavior for when the 'Destination' property value is is > "flowfile-attributes" is even visible when the 'Destination' property value > is is "flowfile-content". This is not necessary and could be confusing. This > ticket aims to only display the "Path Not Found Behavior" property when the > "Destination" property value is flowfile-attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12784) Only display 'Path Not Found Behavior' property in EvaluateJsonPath when 'Destination' property value is flowfile-attributes
[ https://issues.apache.org/jira/browse/NIFI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819066#comment-17819066 ] ASF subversion and git services commented on NIFI-12784: Commit 85f2af438b559c19f2339a2b9fdbe5e31ab44181 in nifi's branch refs/heads/support/nifi-1.x from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=85f2af438b ] NIFI-12784 Set Path Not Found as a Dependent Property in EvaluateJsonPath This closes #8420 Signed-off-by: David Handermann (cherry picked from commit 0a2ba317c0dc0db3a45a904d88802dde1a68304e) > Only display 'Path Not Found Behavior' property in EvaluateJsonPath when > 'Destination' property value is flowfile-attributes > > > Key: NIFI-12784 > URL: https://issues.apache.org/jira/browse/NIFI-12784 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Labels: backport-needed > Time Spent: 20m > Remaining Estimate: 0h > > Currently in EvaluateJsonPath the 'Path Not Found Behavior' property which > defines behavior for when the 'Destination' property value is is > "flowfile-attributes" is even visible when the 'Destination' property value > is is "flowfile-content". This is not necessary and could be confusing. This > ticket aims to only display the "Path Not Found Behavior" property when the > "Destination" property value is flowfile-attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12784) Only display 'Path Not Found Behavior' property in EvaluateJsonPath when 'Destination' property value is flowfile-attributes
[ https://issues.apache.org/jira/browse/NIFI-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819065#comment-17819065 ] ASF subversion and git services commented on NIFI-12784: Commit 0a2ba317c0dc0db3a45a904d88802dde1a68304e in nifi's branch refs/heads/main from dan-s1 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0a2ba317c0 ] NIFI-12784 Set Path Not Found as a Dependent Property in EvaluateJsonPath This closes #8420 Signed-off-by: David Handermann > Only display 'Path Not Found Behavior' property in EvaluateJsonPath when > 'Destination' property value is flowfile-attributes > > > Key: NIFI-12784 > URL: https://issues.apache.org/jira/browse/NIFI-12784 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Labels: backport-needed > Time Spent: 20m > Remaining Estimate: 0h > > Currently in EvaluateJsonPath the 'Path Not Found Behavior' property which > defines behavior for when the 'Destination' property value is is > "flowfile-attributes" is even visible when the 'Destination' property value > is is "flowfile-content". This is not necessary and could be confusing. This > ticket aims to only display the "Path Not Found Behavior" property when the > "Destination" property value is flowfile-attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12784 Refactored to have EvaluateJsonPath's "Path Not Found Behavior" property be dependent on the "Destination" property when its value is "flowfile-attribute" [nifi]
exceptionfactory closed pull request #8420: NIFI-12784 Refactored to have EvaluateJsonPath's "Path Not Found Behavior" property be dependent on the "Destination" property when its value is "flowfile-attribute" URL: https://github.com/apache/nifi/pull/8420 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12633) GetSolr processor clears state on startup
[ https://issues.apache.org/jira/browse/NIFI-12633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann reassigned NIFI-12633: --- Assignee: rob_pr > GetSolr processor clears state on startup > - > > Key: NIFI-12633 > URL: https://issues.apache.org/jira/browse/NIFI-12633 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M1 >Reporter: rob_pr >Assignee: rob_pr >Priority: Major > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The GetSolr processor from nifi-solr stores the latest date of a configured > field so that the same data will not be fetched multiple times. When the user > changes relevant properties, the state is cleared automatically and it starts > fetching records from the beginning. > This also happens unexpectedly when the processor is loaded after > (re)starting NiFi since setting up the properties is incorrectly regarded as > a configuration change. This leads to fetching old records every time NiFi is > restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12633) GetSolr processor clears state on startup
[ https://issues.apache.org/jira/browse/NIFI-12633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12633: Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > GetSolr processor clears state on startup > - > > Key: NIFI-12633 > URL: https://issues.apache.org/jira/browse/NIFI-12633 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M1 >Reporter: rob_pr >Priority: Major > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The GetSolr processor from nifi-solr stores the latest date of a configured > field so that the same data will not be fetched multiple times. When the user > changes relevant properties, the state is cleared automatically and it starts > fetching records from the beginning. > This also happens unexpectedly when the processor is loaded after > (re)starting NiFi since setting up the properties is incorrectly regarded as > a configuration change. This leads to fetching old records every time NiFi is > restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12633) GetSolr processor clears state on startup
[ https://issues.apache.org/jira/browse/NIFI-12633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819060#comment-17819060 ] ASF subversion and git services commented on NIFI-12633: Commit 043e2dd3fff51605f210ada9a5ffab655eafc30a in nifi's branch refs/heads/main from Robert [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=043e2dd3ff ] NIFI-12633 Avoid resetting state in GetSolr on restart This closes #8267 Signed-off-by: David Handermann > GetSolr processor clears state on startup > - > > Key: NIFI-12633 > URL: https://issues.apache.org/jira/browse/NIFI-12633 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M1 >Reporter: rob_pr >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > The GetSolr processor from nifi-solr stores the latest date of a configured > field so that the same data will not be fetched multiple times. When the user > changes relevant properties, the state is cleared automatically and it starts > fetching records from the beginning. > This also happens unexpectedly when the processor is loaded after > (re)starting NiFi since setting up the properties is incorrectly regarded as > a configuration change. This leads to fetching old records every time NiFi is > restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12633 GetSolr processor clears state on startup [nifi]
exceptionfactory closed pull request #8267: NIFI-12633 GetSolr processor clears state on startup URL: https://github.com/apache/nifi/pull/8267 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12827: Component/s: Extensions NiFi Registry > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.26.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12827: Labels: Testing (was: ) > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Labels: Testing > Fix For: 2.0.0, 1.26.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12827. - Resolution: Fixed > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.26.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819056#comment-17819056 ] ASF subversion and git services commented on NIFI-12827: Commit e2d029dd18fad2a03188eac94bee8354554be5c8 in nifi's branch refs/heads/support/nifi-1.x from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e2d029dd18 ] NIFI-12827 Upgraded PostgreSQL JDBC test driver from 42.6.0 to 42.7.2 This closes #8436 Signed-off-by: David Handermann (cherry picked from commit a95f327b3110af4cf5e438fc55aab2d34b055e28) > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.26.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819054#comment-17819054 ] ASF subversion and git services commented on NIFI-12827: Commit 47290eb39fa91fdba3b37f13d91eaa0e82911727 in nifi's branch refs/heads/main from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=47290eb39f ] NIFI-12827 Upgraded PostgreSQL JDBC test driver from 42.7.1 to 42.7.2 This closes #8437 Signed-off-by: David Handermann > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.26.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
[ https://issues.apache.org/jira/browse/NIFI-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819055#comment-17819055 ] ASF subversion and git services commented on NIFI-12827: Commit a95f327b3110af4cf5e438fc55aab2d34b055e28 in nifi's branch refs/heads/main from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a95f327b31 ] NIFI-12827 Upgraded PostgreSQL JDBC test driver from 42.6.0 to 42.7.2 This closes #8436 Signed-off-by: David Handermann > Upgrade PostgresSQL JDBC to 42.7.2 > -- > > Key: NIFI-12827 > URL: https://issues.apache.org/jira/browse/NIFI-12827 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.26.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL > injection using a non-default configuration property. The PostgreSQL JDBC > Driver is not distributed in any NiFi components, it is only used as a > dependency for integration tests, but it should be upgraded to avoid warnings > related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12827 Bump org.postgresql:postgresql from 42.6.0 to 42.7.2 in /nifi-registry/nifi-registry-core/nifi-registry-test [nifi]
dependabot[bot] commented on PR #8436: URL: https://github.com/apache/nifi/pull/8436#issuecomment-1955814917 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12827 Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors [nifi]
dependabot[bot] commented on PR #8437: URL: https://github.com/apache/nifi/pull/8437#issuecomment-1955814908 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12827 Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors [nifi]
exceptionfactory closed pull request #8437: NIFI-12827 Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors URL: https://github.com/apache/nifi/pull/8437 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12827 Bump org.postgresql:postgresql from 42.6.0 to 42.7.2 in /nifi-registry/nifi-registry-core/nifi-registry-test [nifi]
exceptionfactory closed pull request #8436: NIFI-12827 Bump org.postgresql:postgresql from 42.6.0 to 42.7.2 in /nifi-registry/nifi-registry-core/nifi-registry-test URL: https://github.com/apache/nifi/pull/8436 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12827 Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors [nifi]
exceptionfactory commented on PR #8437: URL: https://github.com/apache/nifi/pull/8437#issuecomment-1955807626 Thanks @mattyb149, the 42.7.2 version is now available in Maven, I created NIFI-12827 for tracking and will proceed with merging. https://repo1.maven.org/maven2/org/postgresql/postgresql/42.7.2/ -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12827) Upgrade PostgresSQL JDBC to 42.7.2
David Handermann created NIFI-12827: --- Summary: Upgrade PostgresSQL JDBC to 42.7.2 Key: NIFI-12827 URL: https://issues.apache.org/jira/browse/NIFI-12827 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0, 1.26.0 The PostgreSQL JDBC Driver in versions prior to 42.7.2 is vulnerable to SQL injection using a non-default configuration property. The PostgreSQL JDBC Driver is not distributed in any NiFi components, it is only used as a dependency for integration tests, but it should be upgraded to avoid warnings related to CVE-2024-1597. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12768) Intermittent Failures in TestListFile.testFilterAge
[
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-12768.
-
Resolution: Fixed
> Intermittent Failures in TestListFile.testFilterAge
> ---
>
> Key: NIFI-12768
> URL: https://issues.apache.org/jira/browse/NIFI-12768
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but
> it has begun to fail more recently across multiple platforms on GitHub Action
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge --
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
> at
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so
> the problem appears to be related to these timing calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12768) Intermittent Failures in TestListFile.testFilterAge
[
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819051#comment-17819051
]
ASF subversion and git services commented on NIFI-12768:
Commit 3f2f5a02e05dbb2bd706613e648b9c562a34785a in nifi's branch
refs/heads/main from Joe Witt
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3f2f5a02e0 ]
NIFI-12768 Removed unstable assertions from TestListFile
Additional assertion removals which assumed ordering that isn't guaranteed or
enforced by the tests
This closes #8438
Signed-off-by: David Handermann
> Intermittent Failures in TestListFile.testFilterAge
> ---
>
> Key: NIFI-12768
> URL: https://issues.apache.org/jira/browse/NIFI-12768
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but
> it has begun to fail more recently across multiple platforms on GitHub Action
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge --
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
> at
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so
> the problem appears to be related to these timing calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12768 additional assertion removals which assumed ordering that … [nifi]
exceptionfactory closed pull request #8438: NIFI-12768 additional assertion removals which assumed ordering that … URL: https://github.com/apache/nifi/pull/8438 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12826) Unstable test TestFTP testListFtpHostPortVariablesFileFound
[
https://issues.apache.org/jira/browse/NIFI-12826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-12826:
Summary: Unstable test TestFTP testListFtpHostPortVariablesFileFound (was:
Unstable test)
> Unstable test TestFTP testListFtpHostPortVariablesFileFound
> ---
>
> Key: NIFI-12826
> URL: https://issues.apache.org/jira/browse/NIFI-12826
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
>
> {noformat}
> Error:
> org.apache.nifi.processors.standard.TestFTP.testListFtpHostPortVariablesFileFound
> -- Time elapsed: 0.232 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
> at
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:404)
> at
> org.apache.nifi.processors.standard.TestFTP.testListFtpHostPortVariablesFileFound(TestFTP.java:319)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> Failed in a random build
> https://github.com/apache/nifi/actions/runs/7981892840/job/2179960?pr=8438
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12826) Unstable test
Joe Witt created NIFI-12826:
---
Summary: Unstable test
Key: NIFI-12826
URL: https://issues.apache.org/jira/browse/NIFI-12826
Project: Apache NiFi
Issue Type: Improvement
Reporter: Joe Witt
Assignee: Joe Witt
{noformat}
Error:
org.apache.nifi.processors.standard.TestFTP.testListFtpHostPortVariablesFileFound
-- Time elapsed: 0.232 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
at
org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:404)
at
org.apache.nifi.processors.standard.TestFTP.testListFtpHostPortVariablesFileFound(TestFTP.java:319)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
{noformat}
Failed in a random build
https://github.com/apache/nifi/actions/runs/7981892840/job/2179960?pr=8438
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors [nifi]
mattyb149 commented on PR #8437: URL: https://github.com/apache/nifi/pull/8437#issuecomment-1955577830 42.7.2 hasn't been released to Maven yet and there are no changelogs. Recommend when that happens we close this PR and write up a Jira and a PR. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12825: implemented ListHBaseRegions processor [nifi]
emiliosetiadarma opened a new pull request, #8439: URL: https://github.com/apache/nifi/pull/8439 # Summary [NIFI-12825](https://issues.apache.org/jira/browse/NIFI-12825) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12825) Implement processor to get row key ranges for HBase regions
Emilio Setiadarma created NIFI-12825: Summary: Implement processor to get row key ranges for HBase regions Key: NIFI-12825 URL: https://issues.apache.org/jira/browse/NIFI-12825 Project: Apache NiFi Issue Type: New Feature Reporter: Emilio Setiadarma Assignee: Emilio Setiadarma A common way for parallelizing scan operations to HBase is to scan by row key ranges. In the HBase architecture, HBase splits tables into regions, each with a range of row keys. These row key ranges are mutually exclusive, and they include all the row keys. The manual approach currently to parallelize scans to HBase via row key ranges is to go to HBase shell, perform the "list_regions" function to obtain row key ranges. This approach has its downsides, most importantly being the fact that row key ranges are not static. HBase regions may also split, creating two regions with the row key range split in the middle. Providing a way for NiFi to obtain these row key ranges per HBase region could help improve the ease of creating a flow that performs scans to HBase parallelized by row key range. Once we know row key ranges, this information could be easily fed into a scanning processor (i.e. ScanHBase). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12768 additional assertion removals which assumed ordering that … [nifi]
joewitt opened a new pull request, #8438: URL: https://github.com/apache/nifi/pull/8438 …isn't guaranteed or enforced by the tests # Summary [NIFI-12768](https://issues.apache.org/jira/browse/NIFI-12768) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12768) Intermittent Failures in TestListFile.testFilterAge
[
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819019#comment-17819019
]
Joe Witt commented on NIFI-12768:
-
New PR will remove the same pattern of checks in the same test but preceding
the change already made in this JIRA. It presumes ordering that isn't
guaranteed which makes these already timing dependent tests worse.
> Intermittent Failures in TestListFile.testFilterAge
> ---
>
> Key: NIFI-12768
> URL: https://issues.apache.org/jira/browse/NIFI-12768
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but
> it has begun to fail more recently across multiple platforms on GitHub Action
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge --
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
> at
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so
> the problem appears to be related to these timing calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.postgresql:postgresql from 42.7.1 to 42.7.2 in /nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors [nifi]
dependabot[bot] opened a new pull request, #8437: URL: https://github.com/apache/nifi/pull/8437 Bumps [org.postgresql:postgresql](https://github.com/pgjdbc/pgjdbc) from 42.7.1 to 42.7.2. Changelog Sourced from https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md";>org.postgresql:postgresql's changelog. Changelog Notable changes since version 42.0.0, read the complete https://jdbc.postgresql.org/documentation/changelog.html";>History of Changes. The format is based on http://keepachangelog.com/en/1.0.0/";>Keep a Changelog. [Unreleased] Changed Added feat: Add PasswordUtil for encrypting passwords client side [PR https://redirect.github.com/pgjdbc/pgjdbc/issues/3082";>#3082](https://redirect.github.com/pgjdbc/pgjdbc/pull/3082";>pgjdbc/pgjdbc#3082) Fixed Commits See full diff in https://github.com/pgjdbc/pgjdbc/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/nifi/network/alerts). -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.postgresql:postgresql from 42.6.0 to 42.7.2 in /nifi-registry/nifi-registry-core/nifi-registry-test [nifi]
dependabot[bot] opened a new pull request, #8436: URL: https://github.com/apache/nifi/pull/8436 Bumps [org.postgresql:postgresql](https://github.com/pgjdbc/pgjdbc) from 42.6.0 to 42.7.2. Release notes Sourced from https://github.com/pgjdbc/pgjdbc/releases";>org.postgresql:postgresql's releases. v42.7.1 Fixed regressions since 42.7.0 Revert "Use canonical DateStyle name (https://redirect.github.com/pgjdbc/pgjdbc/issues/2925";>#2925)" https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3035";>#3035) Revert "feat: support SET statements combining with other queries with semicolon in PreparedStatement" https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3010";>#3010) chore: use java.release=8 when building pgjdbc from the generated source distribution https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3038";>#3038), the driver uses Java 8 methods only Changes Apply connectTimeout before SSLSocket.startHandshake to avoid infinite wait in case the connection is broken https://github.com/davecramer";>@davecramer (https://redirect.github.com/pgjdbc/pgjdbc/issues/3040";>#3040) perf: improve performance of PreparedStatement.setBlob, BlobInputStream, and BlobOutputStream with dynamic buffer sizing https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3044";>#3044) fix: avoid timezone conversions when sending LocalDateTime to the database https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/2852";>#2852) fix: support waffle-jna 2.x and 3.x by using reflective approach for ManagedSecBufferDesc https://github.com/chrullrich";>@chrullrich (https://redirect.github.com/pgjdbc/pgjdbc/issues/2720";>#2720) 🧰 Maintenance chore: bump Gradle to 8.5 https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3045";>#3045) chore: use Java 17 for building pgjdbc, and use --release 8 to target Java 8, add tests with Java 21 and 22 https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3026";>#3026) fedora/rpm: move source build to java-17-openjdk-devel https://github.com/praiskup";>@praiskup (https://redirect.github.com/pgjdbc/pgjdbc/issues/3036";>#3036) Update site 42 7 0 https://github.com/davecramer";>@davecramer (https://redirect.github.com/pgjdbc/pgjdbc/issues/3004";>#3004) prepared for release 42.7.1 update changelogs https://github.com/davecramer";>@davecramer (https://redirect.github.com/pgjdbc/pgjdbc/issues/3037";>#3037) ⬆️ Dependencies fix(deps): update dependency org.checkerframework:org.checkerframework.gradle.plugin to v0.6.36 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3060";>#3060) chore(deps): update plugin biz.aqute.bnd.builder to v7 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3034";>#3034) fix(deps): update dependency com.github.spotbugs:com.github.spotbugs.gradle.plugin to v6 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3056";>#3056) fix(deps): update dependency com.github.spotbugs:com.github.spotbugs.gradle.plugin to v5.2.5 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3032";>#3032) chore(deps): update codecov/codecov-action digest to b0466b4 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3059";>#3059) fix(deps): update checkerframework to v3.41.0 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3058";>#3058) fix(deps): update logback to v1.2.13 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3053";>#3053) chore(deps): update codecov/codecov-action digest to 438fa9e https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3051";>#3051) fix(deps): update dependency spotbugs to v4.8.2 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3052";>#3052) chore: bump Gradle to 8.5 https://github.com/vlsi";>@vlsi (https://redirect.github.com/pgjdbc/pgjdbc/issues/3045";>#3045) fix(deps): update dependency org.ops4j.pax.url:pax-url-aether to v2.6.14 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3030";>#3030) chore(deps): update plugin org.nosphere.gradle.github.actions to v1.4.0 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3031";>#3031) chore(deps): update dependency ubuntu to v22 https://github.com/renovate-bot";>@renovate-bot (https://redirect.github.com/pgjdbc/pgjdbc/issues/3033";>#3033) fix(deps): up
Re: [PR] Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 [nifi]
joewitt commented on PR #8435: URL: https://github.com/apache/nifi/pull/8435#issuecomment-1955438428 This change as-is cannot work because of a regression in how compress 1.26 builds. When 1.26.1 comes out in a few days we will take that in -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 [nifi]
dependabot[bot] commented on PR #8435: URL: https://github.com/apache/nifi/pull/8435#issuecomment-1955437479 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 [nifi]
joewitt closed pull request #8435: Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 URL: https://github.com/apache/nifi/pull/8435 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 [nifi]
dependabot[bot] opened a new pull request, #8435: URL: https://github.com/apache/nifi/pull/8435 Bumps org.apache.commons:commons-compress from 1.25.0 to 1.26.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/nifi/network/alerts). -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12824) Remove ExecuteStateless Processor
[
https://issues.apache.org/jira/browse/NIFI-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819018#comment-17819018
]
ASF subversion and git services commented on NIFI-12824:
Commit 014d539b5e63a825c7370d3b242c204e252a167c in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=014d539b5e ]
NIFI-12824 Removed ExecuteStateless Processor and NAR
This closes #8434
Removed nifi-stateless-nar from nifi-assembly
Signed-off-by: Joseph Witt
> Remove ExecuteStateless Processor
> -
>
> Key: NIFI-12824
> URL: https://issues.apache.org/jira/browse/NIFI-12824
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{ExecuteStateless}} Processor and the {{nifi-stateless-processor-nar}}
> should be removed from the main branch as part of preparation for NiFi 2.0.0.
> The {{ExecuteStateless}} Processor provided a transitional solution prior to
> Stateless Execution of Process Groups in standard NiFi deployments. Now that
> Stateless Execution is implemented, the Processor should be removed. As the
> NiFi 2.0.0-M1 and 2.0.0-M2 releases include both the {{ExecuteStateless}}
> Processor and Stateless Execution options, those releases can provide a
> transitional step for deployments that need to have both options available
> for an interim migration approach.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-12824) Remove ExecuteStateless Processor
[
https://issues.apache.org/jira/browse/NIFI-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt resolved NIFI-12824.
-
Resolution: Fixed
> Remove ExecuteStateless Processor
> -
>
> Key: NIFI-12824
> URL: https://issues.apache.org/jira/browse/NIFI-12824
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ExecuteStateless}} Processor and the {{nifi-stateless-processor-nar}}
> should be removed from the main branch as part of preparation for NiFi 2.0.0.
> The {{ExecuteStateless}} Processor provided a transitional solution prior to
> Stateless Execution of Process Groups in standard NiFi deployments. Now that
> Stateless Execution is implemented, the Processor should be removed. As the
> NiFi 2.0.0-M1 and 2.0.0-M2 releases include both the {{ExecuteStateless}}
> Processor and Stateless Execution options, those releases can provide a
> transitional step for deployments that need to have both options available
> for an interim migration approach.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12824 Remove ExecuteStateless Processor and NAR [nifi]
asfgit closed pull request #8434: NIFI-12824 Remove ExecuteStateless Processor and NAR URL: https://github.com/apache/nifi/pull/8434 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12824 Remove ExecuteStateless Processor and NAR [nifi]
joewitt commented on PR #8434: URL: https://github.com/apache/nifi/pull/8434#issuecomment-1955422020 The stinkin test failures are unrelated and are a goofy test problem like NIFI-12768. The full clean build plus integration tests is great and the size drops 30 MB. Good stuff -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12768) Intermittent Failures in TestListFile.testFilterAge
[
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819016#comment-17819016
]
Joe Witt commented on NIFI-12768:
-
Reopened since this JIRA/fix is still on this unreleased line. But a very
similar problem remains in a similar test.
{code:java}
Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge -- Time
elapsed: 6.302 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <2> but was: <3>
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
at
org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:319)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
{code}
> Intermittent Failures in TestListFile.testFilterAge
> ---
>
> Key: NIFI-12768
> URL: https://issues.apache.org/jira/browse/NIFI-12768
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but
> it has begun to fail more recently across multiple platforms on GitHub Action
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge --
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
> at
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so
> the problem appears to be related to these timing calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (NIFI-12768) Intermittent Failures in TestListFile.testFilterAge
[
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt reopened NIFI-12768:
-
> Intermittent Failures in TestListFile.testFilterAge
> ---
>
> Key: NIFI-12768
> URL: https://issues.apache.org/jira/browse/NIFI-12768
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but
> it has begun to fail more recently across multiple platforms on GitHub Action
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error: org.apache.nifi.processors.standard.TestListFile.testFilterAge --
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
> at
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so
> the problem appears to be related to these timing calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12824 Remove ExecuteStateless Processor and NAR [nifi]
joewitt commented on PR #8434: URL: https://github.com/apache/nifi/pull/8434#issuecomment-1955337662 Was going to note only a minor adjustment in total build size which surprised me. And then I see another commit to remove the stateless nar which presumably means the stateless capabilities are nicely baked into the framework itself. Well played! -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-3785 Added feature to move a controller service to it's parent o… [nifi]
markap14 commented on PR #7734: URL: https://github.com/apache/nifi/pull/7734#issuecomment-1955220883 @Freedom9339 you mind rebasing against `main` and pushing again? That should kick off the tests against the latest & greatest. I misread the github comments initially, thinking you pushed a rebased commit just a couple days ago. That explains why I can't kick off the build again -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-3785 Added feature to move a controller service to it's parent o… [nifi]
markap14 commented on PR #7734: URL: https://github.com/apache/nifi/pull/7734#issuecomment-1955213676 Oh nice, thanks @Freedom9339 ! This is something that I've wanted for a while. I would definitely want to get a reviewer who knows the UI as well such as @mcgilman or @scottyaslan. I should have a chance to review the backend soon, probably some time this week. But it looks like the system tests failed and some of the unit tests failed as well. Unfortunately, it looks like the logs have already aged off. I'll see if I can reproduce the failures locally, but we'll definitely want to ensure that we get those cleaned up -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12807: Handle clustering in Provenance, Lineage, and Queue Listing [nifi]
rfellows commented on code in PR #8431:
URL: https://github.com/apache/nifi/pull/8431#discussion_r1496514997
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/flow-designer/ui/canvas/header/flow-status/flow-status.component.ts:
##
@@ -55,8 +56,8 @@ export class FlowStatus {
getClusterStyle(): string {
if (
-!this.clusterSummary.connectedToCluster ||
-this.clusterSummary.connectedNodeCount !=
this.clusterSummary.totalNodeCount
+this.clusterSummary?.connectedToCluster === false ||
+this.clusterSummary?.connectedNodeCount !=
this.clusterSummary?.totalNodeCount
Review Comment:
It looks like the icon used in this scenario isn't colorized as it is in
original NiFi. We don't seem to have a `warning` style defined to make it our
warning/error red.
https://github.com/apache/nifi/assets/713866/627acc3b-03d5-49a2-9814-2befa1b1255a";>
vs.
https://github.com/apache/nifi/assets/713866/8170bfde-827c-45c5-8366-ed6039f65e26";>
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/provenance/state/provenance-event-listing/provenance-event-listing.effects.ts:
##
@@ -237,9 +254,24 @@ export class ProvenanceEventListingEffects {
this.store.select(selectTimeOffset),
this.store.select(selectProvenanceOptions),
this.store.select(selectProvenanceRequest),
-this.store.select(selectAbout).pipe(isDefinedAndNotNull())
+this.store.select(selectAbout).pipe(isDefinedAndNotNull()),
+
this.store.select(selectClusterSummary).pipe(isDefinedAndNotNull())
]),
-tap(([, timeOffset, options, currentRequest, about]) => {
+tap(([, timeOffset, options, currentRequest, about,
clusterSummary]) => {
+let clusterNodes$: Observable;
+if (clusterSummary.connectedToCluster) {
+clusterNodes$ =
this.clusterService.searchCluster().pipe(
+tap({
+error: (errorResponse: HttpErrorResponse) => {
+
this.store.dispatch(ErrorActions.snackBarError({ error: errorResponse.error }));
+}
+}),
Review Comment:
Handling the error in the `tap` here results in a behavior where the error
response is still available to the subscribing consumer and not handled. In
this case, that is `provenance-search-dialog.component.ts:61`. This fails, the
dialog opens and there are no nodes to select as search criteria.
We probably should not even open the dialog if this query fails.
--
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: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12824 Remove ExecuteStateless Processor and NAR [nifi]
joewitt commented on PR #8434: URL: https://github.com/apache/nifi/pull/8434#issuecomment-1955187321 Thanks for tackling this. Super nice to be able to do this correctly and as desired now with stateless process groups and this saves a good bit of space from the build! Running a build now but the changes appear obvious/correct. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12824 Remove ExecuteStateless Processor and NAR [nifi]
exceptionfactory opened a new pull request, #8434: URL: https://github.com/apache/nifi/pull/8434 # Summary [NIFI-12824](https://issues.apache.org/jira/browse/NIFI-12824) Removes the `ExecuteStateless` Processor and `nifi-stateless-processor-nar` from the main branch in favor of the Stateless execution mode available for any Process Group. The 2.0.0-M1 and 2.0.0-M2 releases include both the `ExecuteStateless` Processor and the Stateless execution mode capabilities, providing a transition path for existing usage of `ExecuteStateless`. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12778) RPG Manage remote ports
[ https://issues.apache.org/jira/browse/NIFI-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12778: --- Status: Patch Available (was: In Progress) > RPG Manage remote ports > --- > > Key: NIFI-12778 > URL: https://issues.apache.org/jira/browse/NIFI-12778 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12232 Corrected Group Component ID Handling for Clustered Flows [nifi]
exceptionfactory commented on PR #8432: URL: https://github.com/apache/nifi/pull/8432#issuecomment-1955167706 Merged in https://github.com/apache/nifi/commit/9ca8bfc7520ceba9f090de1db8c117d8b860184e -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12232 Corrected Group Component ID Handling for Clustered Flows [nifi]
exceptionfactory closed pull request #8432: NIFI-12232 Corrected Group Component ID Handling for Clustered Flows URL: https://github.com/apache/nifi/pull/8432 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [NIFI-12778] manage remote ports [nifi]
scottyaslan opened a new pull request, #8433: URL: https://github.com/apache/nifi/pull/8433 NIFI-12778  -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818999#comment-17818999
]
ASF subversion and git services commented on NIFI-12232:
Commit 9ca8bfc7520ceba9f090de1db8c117d8b860184e in nifi's branch
refs/heads/support/nifi-1.x from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9ca8bfc752 ]
NIFI-12232 Corrected Group Component ID Handling for Clustered Flows
Ensured that if a Process Group doesn't have a Versioned Component ID we use
the ComponentIdLookup to create one based on its Instance ID in the same way
that is done when serializing the flow; this ensures matching ID's when we
synchronize flows across the cluster. Also included some code cleanup around
failure handling on startup
This closes #8432
Signed-off-by: David Handermann
> Frequent "failed to connect node to cluster because local flow controller
> partially updated. Administrator should disconnect node and review flow for
> corruption"
> -
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.23.2
>Reporter: John Joseph
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: image-2023-10-16-16-12-31-027.png,
> image-2024-02-14-13-33-44-354.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi
> when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision
> that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the
> Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In
> {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently
> with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected
> from its configured cluster. The requested change will only be allowed if the
> flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested
> change will only be allowed if the flag to acknowledge the disconnected node
> is set.'*_}}
> The job is configured to run only after all the pods are up and running.
> Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
> to connect node to cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at
> org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at
> org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by:
> org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot change destination of Connection
> because the current destination is running
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at
> org.apache.nifi
[jira] [Updated] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12232:
Fix Version/s: 1.26.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Frequent "failed to connect node to cluster because local flow controller
> partially updated. Administrator should disconnect node and review flow for
> corruption"
> -
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.23.2
>Reporter: John Joseph
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0, 1.26.0
>
> Attachments: image-2023-10-16-16-12-31-027.png,
> image-2024-02-14-13-33-44-354.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi
> when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision
> that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the
> Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In
> {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently
> with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected
> from its configured cluster. The requested change will only be allowed if the
> flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested
> change will only be allowed if the flag to acknowledge the disconnected node
> is set.'*_}}
> The job is configured to run only after all the pods are up and running.
> Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
> to connect node to cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at
> org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at
> org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by:
> org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot change destination of Connection
> because the current destination is running
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at
> org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42)
> at
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1530)
> at
> org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1028)
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: Cannot change destination of
> Connect
Re: [PR] NIFI-12773: Added join and anchored RecordPath function [nifi]
markap14 commented on PR #8391: URL: https://github.com/apache/nifi/pull/8391#issuecomment-1955158350 @ChrisSamo632 thanks for reviewing. Pushed a new commit that addresses your comments above. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12824) Remove ExecuteStateless Processor
David Handermann created NIFI-12824:
---
Summary: Remove ExecuteStateless Processor
Key: NIFI-12824
URL: https://issues.apache.org/jira/browse/NIFI-12824
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: David Handermann
Assignee: David Handermann
Fix For: 2.0.0
The {{ExecuteStateless}} Processor and the {{nifi-stateless-processor-nar}}
should be removed from the main branch as part of preparation for NiFi 2.0.0.
The {{ExecuteStateless}} Processor provided a transitional solution prior to
Stateless Execution of Process Groups in standard NiFi deployments. Now that
Stateless Execution is implemented, the Processor should be removed. As the
NiFi 2.0.0-M1 and 2.0.0-M2 releases include both the {{ExecuteStateless}}
Processor and Stateless Execution options, those releases can provide a
transitional step for deployments that need to have both options available for
an interim migration approach.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-8134 allow unescapeJson Record Path function to recursively convert Maps to Records [nifi]
markap14 commented on code in PR #7745:
URL: https://github.com/apache/nifi/pull/7745#discussion_r1496517940
##
nifi-docs/src/main/asciidoc/record-path-guide.adoc:
##
@@ -945,6 +949,27 @@ The following record path expression would return:
| `unescapeJson(/json_str)` | {"name"="John", "age"=30} (as a Map)
|==
+*Note* that Maps cannot be serialised with a RecordSetWriter.
+
+Given a record such as:
+
+
+{
+ "json_str": "{\"name\":\"John\",\"age\":30,\"addresses\"[{\"address_1\":
\"123 Fake Street\"}]}"
+}
+
+
+The following record path expression would return:
+
+|==
+| RecordPath | Return value
+| `unescapeJson(/json_str, 'false')` | {"name"="John", "age"=30,
"addresses"=[{address_1"="123 Fake Street"}]} (as a Map, with each entry in
"addresses" as a Map)
+| `unescapeJson(/json_str, 'true', 'false')` | {"name": "John", "age": 30,
"addresses"=[{address_1"="123 Fake Street"}]} (as a Record, with each entry in
"addresses" as a Map)
+| `unescapeJson(/json_str, 'true', 'true')` | {"name": "John", "age": 30,
"addresses": [{"address_1": "123 Fake Street"}]} (as a Record, with each entry
in "addresses" as a Record)
+|==
+
+*Note* that Maps cannot be serialised with a RecordSetWriter.
Review Comment:
This is the third time that this is stated in the documentation for
`unescapeJson`. I think stating it once is enough.
##
nifi-docs/src/main/asciidoc/record-path-guide.adoc:
##
@@ -894,7 +894,11 @@ The following record path expression would convert the
record into an escaped JS
=== unescapeJson
Converts a stringified JSON element to a Record, Array or simple field (e.g.
String), using the UTF-8 character set.
-Optionally convert JSON Objects parsed as Maps into Records (defaults to
false).
+Optionally convert JSON Objects parsed as Maps into Records (defaults to
false), recursively (defaults to false).
Review Comment:
Can you clarify this statement? I.e., explicitly state the arguments that
the function takes, their names, and whether or not they are required?
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestUpdateRecord.java:
##
@@ -232,16 +235,20 @@ public void testChangingSchema() throws
InitializationException, IOException {
final JsonTreeReader jsonReader = new JsonTreeReader();
runner.addControllerService("reader", jsonReader);
-final String inputSchemaText = new
String(Files.readAllBytes(Paths.get("src/test/resources/TestUpdateRecord/schema/person-with-name-record.avsc")));
-final String outputSchemaText = new
String(Files.readAllBytes(Paths.get("src/test/resources/TestUpdateRecord/schema/person-with-name-string.avsc")));
+final String inputSchemaText = new String(Files
+
.readAllBytes(Paths.get("src/test/resources/TestUpdateRecord/schema/person-with-name-record.avsc")));
+final String outputSchemaText = new String(Files
+
.readAllBytes(Paths.get("src/test/resources/TestUpdateRecord/schema/person-with-name-string.avsc")));
-runner.setProperty(jsonReader,
SchemaAccessUtils.SCHEMA_ACCESS_STRATEGY,
SchemaAccessUtils.SCHEMA_TEXT_PROPERTY);
+runner.setProperty(jsonReader,
SchemaAccessUtils.SCHEMA_ACCESS_STRATEGY,
+SchemaAccessUtils.SCHEMA_TEXT_PROPERTY);
runner.setProperty(jsonReader, SchemaAccessUtils.SCHEMA_TEXT,
inputSchemaText);
runner.enableControllerService(jsonReader);
final JsonRecordSetWriter jsonWriter = new JsonRecordSetWriter();
runner.addControllerService("writer", jsonWriter);
-runner.setProperty(jsonWriter,
SchemaAccessUtils.SCHEMA_ACCESS_STRATEGY,
SchemaAccessUtils.SCHEMA_TEXT_PROPERTY);
+runner.setProperty(jsonWriter,
SchemaAccessUtils.SCHEMA_ACCESS_STRATEGY,
+SchemaAccessUtils.SCHEMA_TEXT_PROPERTY);
Review Comment:
There are a huge number of edits to this file, but almost all of them appear
to be inserting arbitrary newlines that are not necessary. Can we fix that?
##
nifi-docs/src/main/asciidoc/record-path-guide.adoc:
##
@@ -945,6 +949,27 @@ The following record path expression would return:
| `unescapeJson(/json_str)` | {"name"="John", "age"=30} (as a Map)
|==
+*Note* that Maps cannot be serialised with a RecordSetWriter.
Review Comment:
This seems to be a restatement of the above comment (though the above
comment seems more clear to me). Does it make sense to remove this?
##
nifi-docs/src/main/asciidoc/record-path-guide.adoc:
##
@@ -945,6 +949,27 @@ The following record path expression would return:
| `unescapeJson(/json_str)` | {"name"="John", "age"=30} (as a Map)
|
Re: [PR] NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP [nifi]
EndzeitBegins commented on PR #8390: URL: https://github.com/apache/nifi/pull/8390#issuecomment-1955058004 Thank you for the fast response @joewitt and letting me know. Hey @tombrisland, are you interested to work on a backport for 1.x or should I have a go at it? -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP [nifi]
joewitt commented on PR #8390: URL: https://github.com/apache/nifi/pull/8390#issuecomment-1955047783 @EndzeitBegins It would need a separate JIRA/PR would be needed and I dont think the 'removeIf' language mechanism would work as NiFi 1.x is Java 8 or higher. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP [nifi]
EndzeitBegins commented on PR #8390: URL: https://github.com/apache/nifi/pull/8390#issuecomment-1955041581 Thanks for taking on the merge process @joewitt. Could we backport these changes to the `support/nifi-1.x` branch as well? -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12232 Corrected Group Component ID Handling for Clustered Flows [nifi]
markap14 opened a new pull request, #8432: URL: https://github.com/apache/nifi/pull/8432 Ensured that if a Process Group doesn't have a Versioned Component ID we use the ComponentIdLookup to create one based on its Instance ID in the same way that is done when serializing the flow; this ensures matching ID's when we synchronize flows across the cluster. Also included some code cleanup around failure handling on startup This closes #8406 # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12807: Handle clustering in Provenance, Lineage, and Queue Listing [nifi]
rfellows commented on PR #8431: URL: https://github.com/apache/nifi/pull/8431#issuecomment-1954970273 will review -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-12772) Remote poll batch size not exposed for ListSFTP
[ https://issues.apache.org/jira/browse/NIFI-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt resolved NIFI-12772. - Fix Version/s: 2.0.0 Resolution: Fixed > Remote poll batch size not exposed for ListSFTP > --- > > Key: NIFI-12772 > URL: https://issues.apache.org/jira/browse/NIFI-12772 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.25.0 >Reporter: Tom Brisland >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > I was planning on adding support for a batch size in ListSFTP due to some > issues we're seeing with a large number of files on an SFTP server. > Thankfully, it seems that REMOTE_POLL_BATCH_SIZE is already supported in all > the FTP processor variations, just not exposed in ListSFTP. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12772) Remote poll batch size not exposed for ListSFTP
[ https://issues.apache.org/jira/browse/NIFI-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818972#comment-17818972 ] ASF subversion and git services commented on NIFI-12772: Commit 89b618cc052a19bb4bcdbe8f7067ad996aad614d in nifi's branch refs/heads/main from Tom Brisland [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=89b618cc05 ] NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP This closes #8390. revert max results optimisation + unnecessary import Signed-off-by: Joseph Witt > Remote poll batch size not exposed for ListSFTP > --- > > Key: NIFI-12772 > URL: https://issues.apache.org/jira/browse/NIFI-12772 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.25.0 >Reporter: Tom Brisland >Priority: Minor > Time Spent: 1h 40m > Remaining Estimate: 0h > > I was planning on adding support for a batch size in ListSFTP due to some > issues we're seeing with a large number of files on an SFTP server. > Thankfully, it seems that REMOTE_POLL_BATCH_SIZE is already supported in all > the FTP processor variations, just not exposed in ListSFTP. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP [nifi]
asfgit closed pull request #8390: NIFI-12772 Expose REMOTE_POLL_BATCH_SIZE property for ListSFTP URL: https://github.com/apache/nifi/pull/8390 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12788) Failure to start when specifying network interfaces due to IPv6 host encoding
[
https://issues.apache.org/jira/browse/NIFI-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12788:
Summary: Failure to start when specifying network interfaces due to IPv6
host encoding (was: Failure to start when specifying network interfaces)
> Failure to start when specifying network interfaces due to IPv6 host encoding
> -
>
> Key: NIFI-12788
> URL: https://issues.apache.org/jira/browse/NIFI-12788
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If you configure a network interface in nifi.properties like:
> {code:java}
> nifi.web.https.network.interface.1=lo
> nifi.web.https.network.interface.0=en0 {code}
> It fails start up when trying to print the application URLs because the host
> name from the Jetty Connector may include characters that are invalid to be
> passed in to URI.create...
> {code:java}
> java.lang.IllegalArgumentException: Malformed escape pair at index 23:
> https://0:0:0:0:0:0:0:1%lo:8443/nifi
> at java.base/java.net.URI.create(URI.java:932)
>
>at
> org.apache.nifi.web.server.JettyServer.lambda$getApplicationUrls$11(JettyServer.java:728)
>{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12788) Failure to start when specifying network interfaces
[
https://issues.apache.org/jira/browse/NIFI-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12788:
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Failure to start when specifying network interfaces
> ---
>
> Key: NIFI-12788
> URL: https://issues.apache.org/jira/browse/NIFI-12788
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If you configure a network interface in nifi.properties like:
> {code:java}
> nifi.web.https.network.interface.1=lo
> nifi.web.https.network.interface.0=en0 {code}
> It fails start up when trying to print the application URLs because the host
> name from the Jetty Connector may include characters that are invalid to be
> passed in to URI.create...
> {code:java}
> java.lang.IllegalArgumentException: Malformed escape pair at index 23:
> https://0:0:0:0:0:0:0:1%lo:8443/nifi
> at java.base/java.net.URI.create(URI.java:932)
>
>at
> org.apache.nifi.web.server.JettyServer.lambda$getApplicationUrls$11(JettyServer.java:728)
>{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12788) Failure to start when specifying network interfaces
[
https://issues.apache.org/jira/browse/NIFI-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818952#comment-17818952
]
ASF subversion and git services commented on NIFI-12788:
Commit d35247b7b16b9734012daf9b35a2e4e7323545f7 in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d35247b7b1 ]
NIFI-12788 Avoid host URI encoding errors for Jetty Server Connector
This closes #8404
Signed-off-by: David Handermann
> Failure to start when specifying network interfaces
> ---
>
> Key: NIFI-12788
> URL: https://issues.apache.org/jira/browse/NIFI-12788
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If you configure a network interface in nifi.properties like:
> {code:java}
> nifi.web.https.network.interface.1=lo
> nifi.web.https.network.interface.0=en0 {code}
> It fails start up when trying to print the application URLs because the host
> name from the Jetty Connector may include characters that are invalid to be
> passed in to URI.create...
> {code:java}
> java.lang.IllegalArgumentException: Malformed escape pair at index 23:
> https://0:0:0:0:0:0:0:1%lo:8443/nifi
> at java.base/java.net.URI.create(URI.java:932)
>
>at
> org.apache.nifi.web.server.JettyServer.lambda$getApplicationUrls$11(JettyServer.java:728)
>{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12788 Perform URL encoding on host returned from JettyServer Con… [nifi]
exceptionfactory closed pull request #8404: NIFI-12788 Perform URL encoding on host returned from JettyServer Con… URL: https://github.com/apache/nifi/pull/8404 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12823) Upgrade build Angular to 17.2.0
[ https://issues.apache.org/jira/browse/NIFI-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12823: --- https://github.com/apache/nifi/pull/8418 > Upgrade build Angular to 17.2.0 > --- > > Key: NIFI-12823 > URL: https://issues.apache.org/jira/browse/NIFI-12823 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump undici and @angular-devkit/build-angular in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi [nifi]
mcgilman commented on PR #8418: URL: https://github.com/apache/nifi/pull/8418#issuecomment-1954832055 https://issues.apache.org/jira/browse/NIFI-12823 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12823) Upgrade build Angular to 17.2.0
Matt Gilman created NIFI-12823: -- Summary: Upgrade build Angular to 17.2.0 Key: NIFI-12823 URL: https://issues.apache.org/jira/browse/NIFI-12823 Project: Apache NiFi Issue Type: Sub-task Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12823) Upgrade build Angular to 17.2.0
[ https://issues.apache.org/jira/browse/NIFI-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-12823. Resolution: Fixed > Upgrade build Angular to 17.2.0 > --- > > Key: NIFI-12823 > URL: https://issues.apache.org/jira/browse/NIFI-12823 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) ** Counter table has extra unnecessary can modfiy check * Bulletin Board (NIFI-12560) ** When the bulletin board polls it is missing the offset "after" query parameter * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default * Help (NIFI-12795) * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * Handle linking to components that are not on the canvas * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Load FlowConfiguration in guard * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance (NIFI-12767) ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Upgrade to Angular 17 (NIFI-12790) * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu * Migrate NiFi UI to nx [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to dat
[jira] [Updated] (NIFI-12807) Cluster - Provenance, Lineage, and Queue Listing
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Summary: Cluster - Provenance, Lineage, and Queue Listing (was: Cluster - Provenance) > Cluster - Provenance, Lineage, and Queue Listing > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update the Provenance page handle when the NiFi instance is clustered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12807) Cluster - Provenance, Lineage, and Queue Listing
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Status: Patch Available (was: In Progress) > Cluster - Provenance, Lineage, and Queue Listing > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update the Provenance, Lineage, and Queue Listing page handle when the NiFi > instance is clustered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12807) Cluster - Provenance, Lineage, and Queue Listing
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Description: Update the Provenance, Lineage, and Queue Listing page handle when the NiFi instance is clustered. (was: Update the Provenance page handle when the NiFi instance is clustered.) > Cluster - Provenance, Lineage, and Queue Listing > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update the Provenance, Lineage, and Queue Listing page handle when the NiFi > instance is clustered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump undici and @angular-devkit/build-angular in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi [nifi]
mcgilman merged PR #8418: URL: https://github.com/apache/nifi/pull/8418 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12807: Handle clustering in Provenange, Linage, and Queue Listing [nifi]
mcgilman opened a new pull request, #8431: URL: https://github.com/apache/nifi/pull/8431 NIFI-12807: - Handling cluster node id in provenance listing, lineage graph, and queue listing. - Simplify dev proxy config. - Serve UI at /nifi to mirror actual NiFi deployment. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) ** Counter table has extra unnecessary can modfiy check * Bulletin Board (NIFI-12560) ** When the bulletin board polls it is missing the offset "after" query parameter * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default * Help (NIFI-12795) * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * Handle linking to components that are not on the canvas * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Load FlowConfiguration in guard * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance (NIFI-12767) ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Upgrade to Angular 17 (NIFI-12790) * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu * Migrate NiFi UI to nx [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaini
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) ** Counter table has extra unnecessary can modfiy check * Bulletin Board (NIFI-12560) ** When the bulletin board polls it is missing the offset "after" query parameter * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default * Help (NIFI-12795) * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Component Version * Consider PG permissions in Toolbox (NIFI-12683) * Handle linking to components that are not on the canvas * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Load FlowConfiguration in guard * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance (NIFI-12767) ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Upgrade to Angular 17 (NIFI-12790) * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) * Flow Analysis report menu * Migrate NiFi UI to nx [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and impr
[jira] [Updated] (NIFI-12807) Cluster - Provenance
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Description: Update the Provenance page handle when the NiFi instance is clustered. (was: Update Provenance page handle when the NiFi instance is clustered.) > Cluster - Provenance > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Update the Provenance page handle when the NiFi instance is clustered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12807) Cluster - Provenance
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Description: Update Provenance page handle when the NiFi instance is clustered. (was: When running the dev server with a target backend that is running on a different path, the API calls do not use the correct base path. I believe this is due to its current usage of relative paths. Some changes may be needed to work with the http client in it's intended way.) > Cluster - Provenance > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Update Provenance page handle when the NiFi instance is clustered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12807) Cluster - Provenance
[ https://issues.apache.org/jira/browse/NIFI-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12807: --- Summary: Cluster - Provenance (was: API paths don't work when proxied backend on different path) > Cluster - Provenance > > > Key: NIFI-12807 > URL: https://issues.apache.org/jira/browse/NIFI-12807 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > When running the dev server with a target backend that is running on a > different path, the API calls do not use the correct base path. I believe > this is due to its current usage of relative paths. Some changes may be > needed to work with the http client in it's intended way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818922#comment-17818922
]
David Handermann commented on NIFI-12232:
-
Merged initial PR with corrections to the main branch for NiFi 2.0.0. Based on
other substantive changes to leader election components, a separate PR will be
necessary for the support branch.
> Frequent "failed to connect node to cluster because local flow controller
> partially updated. Administrator should disconnect node and review flow for
> corruption"
> -
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.23.2
>Reporter: John Joseph
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: image-2023-10-16-16-12-31-027.png,
> image-2024-02-14-13-33-44-354.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi
> when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision
> that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the
> Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In
> {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently
> with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected
> from its configured cluster. The requested change will only be allowed if the
> flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested
> change will only be allowed if the flag to acknowledge the disconnected node
> is set.'*_}}
> The job is configured to run only after all the pods are up and running.
> Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
> to connect node to cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at
> org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at
> org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by:
> org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot change destination of Connection
> because the current destination is running
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at
> org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42)
> at
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1530)
> at
> org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(Standa
[jira] [Updated] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12232:
Fix Version/s: 2.0.0
> Frequent "failed to connect node to cluster because local flow controller
> partially updated. Administrator should disconnect node and review flow for
> corruption"
> -
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.23.2
>Reporter: John Joseph
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: image-2023-10-16-16-12-31-027.png,
> image-2024-02-14-13-33-44-354.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi
> when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision
> that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the
> Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In
> {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently
> with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected
> from its configured cluster. The requested change will only be allowed if the
> flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested
> change will only be allowed if the flag to acknowledge the disconnected node
> is set.'*_}}
> The job is configured to run only after all the pods are up and running.
> Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
> to connect node to cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at
> org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at
> org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by:
> org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot change destination of Connection
> because the current destination is running
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at
> org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42)
> at
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1530)
> at
> org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817)
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1028)
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: Cannot change destination of
> Connection because the current destination is running
> at
> org.apache.nifi.connectable.Stan
Re: [PR] NIFI-8134 allow unescapeJson Record Path function to recursively convert Maps to Records [nifi]
markap14 commented on PR #7745: URL: https://github.com/apache/nifi/pull/7745#issuecomment-1954700969 Thanks @ChrisSamo632 will take a look this week -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818917#comment-17818917
]
ASF subversion and git services commented on NIFI-12232:
Commit a821966a870a494bd0a7eb0ae15822e06b8d21c5 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a821966a87 ]
NIFI-12232 Corrected Group Component ID Handling for Clustered Flows
Ensured that if a Process Group doesn't have a Versioned Component ID we use
the ComponentIdLookup to create one based on its Instance ID in the same way
that is done when serializing the flow; this ensures matching ID's when we
synchronize flows across the cluster. Also included some code cleanup around
failure handling on startup
This closes #8406
Signed-off-by: David Handermann
> Frequent "failed to connect node to cluster because local flow controller
> partially updated. Administrator should disconnect node and review flow for
> corruption"
> -
>
> Key: NIFI-12232
> URL: https://issues.apache.org/jira/browse/NIFI-12232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
>Affects Versions: 1.23.2
>Reporter: John Joseph
>Assignee: Mark Payne
>Priority: Major
> Attachments: image-2023-10-16-16-12-31-027.png,
> image-2024-02-14-13-33-44-354.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is an issue that we have been observing in the 1.23.2 version of NiFi
> when we try upgrade,
> Since Rolling upgrade is not supported in NiFi, we scale out the revision
> that is running and {_}run a helm upgrade{_}.
> We have NIFI running in k8s cluster mode, there is a post job that call the
> Tenants and policies API. On a successful run it would run like this
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '200'
> set_policies() Action: 'read' Resource: '/tenants' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'{code}
> *_This job was running fine in 1.23.0, 1.22 and other previous versions._* In
> {*}{{1.23.2}}{*}, we are noticing that the job is failing very frequently
> with the error logs;
> {code:java}
> set_policies() Action: 'read' Resource: '/flow' entity_id:
> 'ad2d3ad6-5d69-3e0f-95e9-c7feb36e2de5' entity_name: 'CN=nifi-api-admin'
> entity_type: 'USER'
> set_policies() status: '200'
> 'read' '/flow' policy already exists. It will be updated...
> set_policies() fetching policy inside -eq 200 status: '200'
> set_policies() after update PUT: '400'
> An error occurred getting 'read' '/flow' policy: 'This node is disconnected
> from its configured cluster. The requested change will only be allowed if the
> flag to acknowledge the disconnected node is set.'{code}
> {{_*'This node is disconnected from its configured cluster. The requested
> change will only be allowed if the flag to acknowledge the disconnected node
> is set.'*_}}
> The job is configured to run only after all the pods are up and running.
> Though the pods are up we see exception is the inside pods
> {code:java}
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
> to connect node to cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667)
> at
> org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107)
> at
> org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by:
> org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot change destination of Connection
> because the current destination is running
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
> at
> org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:206)
> at
> org.apache.nifi.controller.serialization.StandardFlowSynchr
Re: [PR] NIFI-12232: Ensured that if a Process Group doesn't have a Versioned … [nifi]
exceptionfactory closed pull request #8406: NIFI-12232: Ensured that if a Process Group doesn't have a Versioned … URL: https://github.com/apache/nifi/pull/8406 -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12788 Perform URL encoding on host returned from JettyServer Con… [nifi]
bbende commented on code in PR #8404:
URL: https://github.com/apache/nifi/pull/8404#discussion_r1496198434
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-jetty/src/main/java/org/apache/nifi/web/server/JettyServer.java:
##
@@ -724,7 +726,7 @@ protected List getApplicationUrls() {
final String scheme = sslConnectionFactory == null ?
HTTP_SCHEME : HTTPS_SCHEME;
final int port = serverConnector.getLocalPort();
final String connectorHost = serverConnector.getHost();
-final String host =
StringUtils.defaultIfEmpty(connectorHost, HOST_UNSPECIFIED);
+final String host =
URLEncoder.encode(StringUtils.defaultIfEmpty(connectorHost, HOST_UNSPECIFIED),
StandardCharsets.UTF_8);
return URI.create(String.format(APPLICATION_URL_FORMAT,
scheme, host, port));
Review Comment:
Thanks @dan-s1 , that seems like a simpler solution and does appear to work
--
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: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12788 Perform URL encoding on host returned from JettyServer Con… [nifi]
bbende commented on code in PR #8404:
URL: https://github.com/apache/nifi/pull/8404#discussion_r1496198434
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-jetty/src/main/java/org/apache/nifi/web/server/JettyServer.java:
##
@@ -724,7 +726,7 @@ protected List getApplicationUrls() {
final String scheme = sslConnectionFactory == null ?
HTTP_SCHEME : HTTPS_SCHEME;
final int port = serverConnector.getLocalPort();
final String connectorHost = serverConnector.getHost();
-final String host =
StringUtils.defaultIfEmpty(connectorHost, HOST_UNSPECIFIED);
+final String host =
URLEncoder.encode(StringUtils.defaultIfEmpty(connectorHost, HOST_UNSPECIFIED),
StandardCharsets.UTF_8);
return URI.create(String.format(APPLICATION_URL_FORMAT,
scheme, host, port));
Review Comment:
Thanks @dan-s1 , that seems like a simpler solution and does appear to work,
the logs now show:
```
2024-02-20 12:06:40,195 INFO [main] org.apache.nifi.web.server.JettyServer
Started Server on https://[fe80:0:0:0:c6d:9e76:6aff:9d0f%en0]:8443/nifi
2024-02-20 12:06:40,195 INFO [main] org.apache.nifi.web.server.JettyServer
Started Server on https://192.168.1.169:8443/nifi
```
--
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: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (NIFI-12771) Restore Client-side KMS encryption strategy in StandardS3EncryptionService
[ https://issues.apache.org/jira/browse/NIFI-12771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12771: Affects Version/s: 2.0.0-M2 2.0.0-M1 > Restore Client-side KMS encryption strategy in StandardS3EncryptionService > -- > > Key: NIFI-12771 > URL: https://issues.apache.org/jira/browse/NIFI-12771 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 2.0.0-M1, 2.0.0-M2 >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > NIFI-12144 partially removed "Client-side KMS" encryption strategy. The > strategy class and some code were deleted but the option is still available > on the UI, just not works. > It seems it happened unintentionally. Bring back the functionality. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12771) Restore Client-side KMS encryption strategy in StandardS3EncryptionService
[ https://issues.apache.org/jira/browse/NIFI-12771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12771: Component/s: Extensions > Restore Client-side KMS encryption strategy in StandardS3EncryptionService > -- > > Key: NIFI-12771 > URL: https://issues.apache.org/jira/browse/NIFI-12771 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M1, 2.0.0-M2 >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > NIFI-12144 partially removed "Client-side KMS" encryption strategy. The > strategy class and some code were deleted but the option is still available > on the UI, just not works. > It seems it happened unintentionally. Bring back the functionality. -- This message was sent by Atlassian Jira (v8.20.10#820010)
