[jira] [Updated] (NIFI-8664) Upgrade json-path (jayway) dependency
[ https://issues.apache.org/jira/browse/NIFI-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramon Havermans updated NIFI-8664: -- Description: Upgrading to json-path 2.6.0 will allow new features like aggregation. Pull request will follow. See [https://github.com/json-path/JsonPath] for details. was: Upgrading to json-path 2.6.0 will allow new features like aggregation. Pull request will follow. > Upgrade json-path (jayway) dependency > - > > Key: NIFI-8664 > URL: https://issues.apache.org/jira/browse/NIFI-8664 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.13.2 >Reporter: Ramon Havermans >Priority: Minor > > Upgrading to json-path 2.6.0 will allow new features like aggregation. > > Pull request will follow. > > See [https://github.com/json-path/JsonPath] for details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8664) Upgrade json-path (jayway) dependency
[ https://issues.apache.org/jira/browse/NIFI-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramon Havermans updated NIFI-8664: -- Description: Upgrading to json-path 2.6.0 will allow new features like aggregation. Pull request will follow. was: Upgrading to json-path 2.5.0 will allow new features like aggregation. Pull request will follow. > Upgrade json-path (jayway) dependency > - > > Key: NIFI-8664 > URL: https://issues.apache.org/jira/browse/NIFI-8664 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.13.2 >Reporter: Ramon Havermans >Priority: Minor > > Upgrading to json-path 2.6.0 will allow new features like aggregation. > > Pull request will follow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8664) Upgrade json-path (jayway) dependency
Ramon Havermans created NIFI-8664: - Summary: Upgrade json-path (jayway) dependency Key: NIFI-8664 URL: https://issues.apache.org/jira/browse/NIFI-8664 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.13.2 Reporter: Ramon Havermans Upgrading to json-path 2.5.0 will allow new features like aggregation. Pull request will follow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-5422) Make ExecuteScript thread safe & use CompiledScript where possible
[ https://issues.apache.org/jira/browse/NIFI-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramon Havermans updated NIFI-5422: -- Description: In ExcuteScript Bindings are reused, which makes it non thread safe. Most engines can use a Compiled version of the engine, which makes it faster. Pull request will follow. was:In ExcuteScript Bindings are reused, which makes it non thread safe. Most engines can use a Compiled version of the engine, which makes it faster. > Make ExecuteScript thread safe & use CompiledScript where possible > -- > > Key: NIFI-5422 > URL: https://issues.apache.org/jira/browse/NIFI-5422 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Ramon Havermans >Priority: Major > > In ExcuteScript Bindings are reused, which makes it non thread safe. Most > engines can use a Compiled version of the engine, which makes it faster. > Pull request will follow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5422) Make ExecuteScript thread safe & use CompiledScript where possible
Ramon Havermans created NIFI-5422: - Summary: Make ExecuteScript thread safe & use CompiledScript where possible Key: NIFI-5422 URL: https://issues.apache.org/jira/browse/NIFI-5422 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Ramon Havermans In ExcuteScript Bindings are reused, which makes it non thread safe. Most engines can use a Compiled version of the engine, which makes it faster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5370) Cluster request replication failing with wildcard certs
[
https://issues.apache.org/jira/browse/NIFI-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534777#comment-16534777
]
Ramon Havermans commented on NIFI-5370:
---
Same with us, for now fixed it with whole list of possibilities, but scaling
will be bad.
> Cluster request replication failing with wildcard certs
> ---
>
> Key: NIFI-5370
> URL: https://issues.apache.org/jira/browse/NIFI-5370
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.7.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Major
> Labels: certificate, cluster, security, tls, wildcard
>
> From the users mailing list:
> {quote}
> Team,
>
> NiFi secured cluster throws below error with wildcarded self-signed
> standalone certificate. Just a brief background, we are deploying nifi in
> Kubernetes where we have to use wildcarded certificates. Till nifi 1.6.0, it
> was working fine.
> Also I tried bringing up NiFi in linux VM in secured cluster mode with
> wildcarded certs, I am getting same error.
>
> Toolkit command to generate certs:
> bin/tls-toolkit.sh standalone -n
> '*.mynifi-nifi-headless.default.svc.cluster.local’ -C 'CN=admin, OU=NIFI' -o
>
>
> Logs:
> 2018-07-02 12:40:32,369 WARN [Replicate Request Thread-1]
> o.a.n.c.c.h.r.ThreadPoolRequestReplicator Failed to replicate request GET
> /nifi-api/flow/current-user to
> mynifi-nifi-1.mynifi-nifi-headless.default.svc.cluster.local:8443 due to
> javax.net.ssl.SSLPeerUnverifiedException: Hostname
> mynifi-nifi-1.mynifi-nifi-headless.default.svc.cluster.local not verified:
> certificate: sha256/
> DN: CN=*.mynifi-nifi-headless.default.svc.cluster.local, OU=NIFI
> subjectAltNames: [*.mynifi-nifi-headless.default.svc.cluster.local]
> 2018-07-02 12:40:32,370 WARN [Replicate Request Thread-1]
> o.a.n.c.c.h.r.ThreadPoolRequestReplicator
> javax.net.ssl.SSLPeerUnverifiedException: Hostname
> mynifi-nifi-1.mynifi-nifi-headless.default.svc.cluster.local not verified:
> certificate: sha256/
> DN: CN=*.mynifi-nifi-headless.default.svc.cluster.local, OU=NIFI
> subjectAltNames: [*.mynifi-nifi-headless.default.svc.cluster.local]
> at
> okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:316)
>
> Please help me in resolving this.
>
> Note: Same certificates is working for single mode setup.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (NIFI-5314) Use newer version of JsonPath
[ https://issues.apache.org/jira/browse/NIFI-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramon Havermans resolved NIFI-5314. --- Resolution: Duplicate Already on master... > Use newer version of JsonPath > - > > Key: NIFI-5314 > URL: https://issues.apache.org/jira/browse/NIFI-5314 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.6.0 >Reporter: Ramon Havermans >Priority: Minor > Attachments: json-path-functions.png > > > Currently the version of JsonPath doesn't implement the use of functions in > the path (min, max, avg, stddev & length). > In 2.3 its there is this functionality with a limitation. There is a fork of > json-path which does handle it correctly, which is also merged into master of > original json-path, but not merged yet. > I'll supply a pull request to use this newer forked version and also remove > the use of the internal classes of that library. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5314) Use newer version of JsonPath
[ https://issues.apache.org/jira/browse/NIFI-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramon Havermans updated NIFI-5314: -- Attachment: json-path-functions.png > Use newer version of JsonPath > - > > Key: NIFI-5314 > URL: https://issues.apache.org/jira/browse/NIFI-5314 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.6.0 >Reporter: Ramon Havermans >Priority: Minor > Attachments: json-path-functions.png > > > Currently the version of JsonPath doesn't implement the use of functions in > the path (min, max, avg, stddev & length). > In 2.3 its there is this functionality with a limitation. There is a fork of > json-path which does handle it correctly, which is also merged into master of > original json-path, but not merged yet. > I'll supply a pull request to use this newer forked version and also remove > the use of the internal classes of that library. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5314) Use newer version of JsonPath
Ramon Havermans created NIFI-5314: - Summary: Use newer version of JsonPath Key: NIFI-5314 URL: https://issues.apache.org/jira/browse/NIFI-5314 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.6.0 Reporter: Ramon Havermans Currently the version of JsonPath doesn't implement the use of functions in the path (min, max, avg, stddev & length). In 2.3 its there is this functionality with a limitation. There is a fork of json-path which does handle it correctly, which is also merged into master of original json-path, but not merged yet. I'll supply a pull request to use this newer forked version and also remove the use of the internal classes of that library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4092) ClassCastException Warning during cluster sync
[ https://issues.apache.org/jira/browse/NIFI-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16234044#comment-16234044 ] Ramon Havermans commented on NIFI-4092: --- Same here on 1.3 > ClassCastException Warning during cluster sync > -- > > Key: NIFI-4092 > URL: https://issues.apache.org/jira/browse/NIFI-4092 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.3.0 >Reporter: Joseph Gresock >Priority: Major > > This is the strack trace I receive, though I'm not sure it affects anything, > since the cluster is eventually able to connect. > 2017-06-20 13:46:44,680 WARN [Reconnect ip-172-31-55-36.ec2.internal:8443] > o.a.n.c.c.node.NodeClusterCoordinator Problem encountered issuing > reconnection request to node ip-172-31-55-36.ec2.internal:8443 > java.io.IOException: > org.apache.nifi.controller.serialization.FlowSerializationException: > java.lang.ClassCastException: > org.apache.nifi.web.api.dto.TemplateDTO$JaxbAccessorM_getDescription_setDescription_java_lang_String > cannot be cast to com.sun.xml.internal.bind.v2.runtime.reflect.Accessor > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.save(StandardXMLFlowConfigurationDAO.java:143) > at > org.apache.nifi.controller.StandardFlowService.createDataFlowFromController(StandardFlowService.java:607) > at > org.apache.nifi.controller.StandardFlowService.createDataFlowFromController(StandardFlowService.java:100) > at > org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator$2.run(NodeClusterCoordinator.java:706) > at java.lang.Thread.run(Thread.java:748) > Caused by: > org.apache.nifi.controller.serialization.FlowSerializationException: > java.lang.ClassCastException: > org.apache.nifi.web.api.dto.TemplateDTO$JaxbAccessorM_getDescription_setDescription_java_lang_String > cannot be cast to com.sun.xml.internal.bind.v2.runtime.reflect.Accessor > at > org.apache.nifi.controller.serialization.StandardFlowSerializer.addTemplate(StandardFlowSerializer.java:546) > at > org.apache.nifi.controller.serialization.StandardFlowSerializer.addProcessGroup(StandardFlowSerializer.java:203) > at > org.apache.nifi.controller.serialization.StandardFlowSerializer.addProcessGroup(StandardFlowSerializer.java:187) > at > org.apache.nifi.controller.serialization.StandardFlowSerializer.addProcessGroup(StandardFlowSerializer.java:187) > at > org.apache.nifi.controller.serialization.StandardFlowSerializer.serialize(StandardFlowSerializer.java:97) > at > org.apache.nifi.controller.FlowController.serialize(FlowController.java:1544) > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.save(StandardXMLFlowConfigurationDAO.java:141) > ... 4 common frames omitted > Caused by: java.lang.ClassCastException: > org.apache.nifi.web.api.dto.TemplateDTO$JaxbAccessorM_getDescription_setDescription_java_lang_String > cannot be cast to com.sun.xml.internal.bind.v2.runtime.reflect.Accessor > at > com.sun.xml.internal.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.instanciate(OptimizedAccessorFactory.java:190) > at > com.sun.xml.internal.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:129) > at > com.sun.xml.internal.bind.v2.runtime.reflect.Accessor$GetterSetterReflection.optimize(Accessor.java:388) > at > com.sun.xml.internal.bind.v2.runtime.property.SingleElementLeafProperty.(SingleElementLeafProperty.java:77) > at sun.reflect.GeneratedConstructorAccessor435.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at > com.sun.xml.internal.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:113) > at > com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.(ClassBeanInfoImpl.java:166) > at > com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:488) > at > com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:305) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
