[jira] [Created] (NIFI-9143) Refactor nifi-redis-bundle to use JUnit 5
Mike Thomsen created NIFI-9143: -- Summary: Refactor nifi-redis-bundle to use JUnit 5 Key: NIFI-9143 URL: https://issues.apache.org/jira/browse/NIFI-9143 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9141) Refactor nifi-provenance-repository-bundle to use JUnit 5
Mike Thomsen created NIFI-9141: -- Summary: Refactor nifi-provenance-repository-bundle to use JUnit 5 Key: NIFI-9141 URL: https://issues.apache.org/jira/browse/NIFI-9141 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9144) Refactor nifi-registry-bundle to use JUnit 5
Mike Thomsen created NIFI-9144: -- Summary: Refactor nifi-registry-bundle to use JUnit 5 Key: NIFI-9144 URL: https://issues.apache.org/jira/browse/NIFI-9144 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9142) Refactor nifi-ranger-bundle to use JUnit 5
Mike Thomsen created NIFI-9142: -- Summary: Refactor nifi-ranger-bundle to use JUnit 5 Key: NIFI-9142 URL: https://issues.apache.org/jira/browse/NIFI-9142 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9146) Refactor nifi-riemann-bundle to use JUnit 5
Mike Thomsen created NIFI-9146: -- Summary: Refactor nifi-riemann-bundle to use JUnit 5 Key: NIFI-9146 URL: https://issues.apache.org/jira/browse/NIFI-9146 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9138) Refactor nifi-pgp-bundle to use JUnit 5
Mike Thomsen created NIFI-9138: -- Summary: Refactor nifi-pgp-bundle to use JUnit 5 Key: NIFI-9138 URL: https://issues.apache.org/jira/browse/NIFI-9138 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9137) Refactor nifi-parquet-bundle to use JUnit 5
Mike Thomsen created NIFI-9137: -- Summary: Refactor nifi-parquet-bundle to use JUnit 5 Key: NIFI-9137 URL: https://issues.apache.org/jira/browse/NIFI-9137 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9135) Refactor nifi-mqtt-bundle to use JUnit 5
Mike Thomsen created NIFI-9135: -- Summary: Refactor nifi-mqtt-bundle to use JUnit 5 Key: NIFI-9135 URL: https://issues.apache.org/jira/browse/NIFI-9135 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9131) Refactor nifi-ldap-iaa-providers-bundle to use JUnit 5
Mike Thomsen created NIFI-9131: -- Summary: Refactor nifi-ldap-iaa-providers-bundle to use JUnit 5 Key: NIFI-9131 URL: https://issues.apache.org/jira/browse/NIFI-9131 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9130) Refactor nifi-language-translation-bundle to use JUnit 5
Mike Thomsen created NIFI-9130: -- Summary: Refactor nifi-language-translation-bundle to use JUnit 5 Key: NIFI-9130 URL: https://issues.apache.org/jira/browse/NIFI-9130 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9134) Refactor nifi-metrics-reporting-bundle to use JUnit 5
Mike Thomsen created NIFI-9134: -- Summary: Refactor nifi-metrics-reporting-bundle to use JUnit 5 Key: NIFI-9134 URL: https://issues.apache.org/jira/browse/NIFI-9134 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9136) Refactor nifi-network-bundle to use JUnit 5
Mike Thomsen created NIFI-9136: -- Summary: Refactor nifi-network-bundle to use JUnit 5 Key: NIFI-9136 URL: https://issues.apache.org/jira/browse/NIFI-9136 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9129) Refactor nifi-kudu-bundle to use JUnit 5
Mike Thomsen created NIFI-9129: -- Summary: Refactor nifi-kudu-bundle to use JUnit 5 Key: NIFI-9129 URL: https://issues.apache.org/jira/browse/NIFI-9129 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9133) Refactor nifi-media-bundle to use JUnit 5
Mike Thomsen created NIFI-9133: -- Summary: Refactor nifi-media-bundle to use JUnit 5 Key: NIFI-9133 URL: https://issues.apache.org/jira/browse/NIFI-9133 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9132) Refactor nifi-lumberjack-bundle to use JUnit 5
Mike Thomsen created NIFI-9132: -- Summary: Refactor nifi-lumberjack-bundle to use JUnit 5 Key: NIFI-9132 URL: https://issues.apache.org/jira/browse/NIFI-9132 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9127) Refactor nifi-kerberos-iaa-providers-bundle to use JUnit 5
Mike Thomsen created NIFI-9127: -- Summary: Refactor nifi-kerberos-iaa-providers-bundle to use JUnit 5 Key: NIFI-9127 URL: https://issues.apache.org/jira/browse/NIFI-9127 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9122) Refactor nifi-influxdb-bundle to use JUnit 5
Mike Thomsen created NIFI-9122: -- Summary: Refactor nifi-influxdb-bundle to use JUnit 5 Key: NIFI-9122 URL: https://issues.apache.org/jira/browse/NIFI-9122 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9125) Refactor nifi-jolt-record-bundle to use JUnit 5
Mike Thomsen created NIFI-9125: -- Summary: Refactor nifi-jolt-record-bundle to use JUnit 5 Key: NIFI-9125 URL: https://issues.apache.org/jira/browse/NIFI-9125 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9118) Refactor nifi-hive-bundle to use JUnit 5
Mike Thomsen created NIFI-9118: -- Summary: Refactor nifi-hive-bundle to use JUnit 5 Key: NIFI-9118 URL: https://issues.apache.org/jira/browse/NIFI-9118 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9121) Refactor nifi-ignite-bundle to use JUnit 5
Mike Thomsen created NIFI-9121: -- Summary: Refactor nifi-ignite-bundle to use JUnit 5 Key: NIFI-9121 URL: https://issues.apache.org/jira/browse/NIFI-9121 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9119) Refactor nifi-hl7-bundle to use JUnit 5
Mike Thomsen created NIFI-9119: -- Summary: Refactor nifi-hl7-bundle to use JUnit 5 Key: NIFI-9119 URL: https://issues.apache.org/jira/browse/NIFI-9119 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9126) Refactor nifi-kafka-bundle to use JUnit 5
Mike Thomsen created NIFI-9126: -- Summary: Refactor nifi-kafka-bundle to use JUnit 5 Key: NIFI-9126 URL: https://issues.apache.org/jira/browse/NIFI-9126 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9123) Refactor nifi-jetty-bundle to use JUnit 5
Mike Thomsen created NIFI-9123: -- Summary: Refactor nifi-jetty-bundle to use JUnit 5 Key: NIFI-9123 URL: https://issues.apache.org/jira/browse/NIFI-9123 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9120) Refactor nifi-html-bundle to use JUnit 5
Mike Thomsen created NIFI-9120: -- Summary: Refactor nifi-html-bundle to use JUnit 5 Key: NIFI-9120 URL: https://issues.apache.org/jira/browse/NIFI-9120 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9124) Refactor nifi-jms-bundle to use JUnit 5
Mike Thomsen created NIFI-9124: -- Summary: Refactor nifi-jms-bundle to use JUnit 5 Key: NIFI-9124 URL: https://issues.apache.org/jira/browse/NIFI-9124 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9128) Refactor nifi-kite-bundle to use JUnit 5
Mike Thomsen created NIFI-9128: -- Summary: Refactor nifi-kite-bundle to use JUnit 5 Key: NIFI-9128 URL: https://issues.apache.org/jira/browse/NIFI-9128 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9117) Refactor nifi-hbase-bundle to use JUnit 5
Mike Thomsen created NIFI-9117: -- Summary: Refactor nifi-hbase-bundle to use JUnit 5 Key: NIFI-9117 URL: https://issues.apache.org/jira/browse/NIFI-9117 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9113) Refactor nifi-grpc-bundle to use JUnit 5
Mike Thomsen created NIFI-9113: -- Summary: Refactor nifi-grpc-bundle to use JUnit 5 Key: NIFI-9113 URL: https://issues.apache.org/jira/browse/NIFI-9113 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9111) Refactor nifi-gcp-bundle to use JUnit 5
Mike Thomsen created NIFI-9111: -- Summary: Refactor nifi-gcp-bundle to use JUnit 5 Key: NIFI-9111 URL: https://issues.apache.org/jira/browse/NIFI-9111 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9116) Refactor nifi-hazelcast-bundle to use JUnit 5
Mike Thomsen created NIFI-9116: -- Summary: Refactor nifi-hazelcast-bundle to use JUnit 5 Key: NIFI-9116 URL: https://issues.apache.org/jira/browse/NIFI-9116 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9115) Refactor nifi-hadoop-libraries-bundle to use JUnit 5
Mike Thomsen created NIFI-9115: -- Summary: Refactor nifi-hadoop-libraries-bundle to use JUnit 5 Key: NIFI-9115 URL: https://issues.apache.org/jira/browse/NIFI-9115 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9114) Refactor nifi-hadoop-bundle to use JUnit 5
Mike Thomsen created NIFI-9114: -- Summary: Refactor nifi-hadoop-bundle to use JUnit 5 Key: NIFI-9114 URL: https://issues.apache.org/jira/browse/NIFI-9114 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9112) Refactor nifi-groovxy-bundle to use JUnit 5
Mike Thomsen created NIFI-9112: -- Summary: Refactor nifi-groovxy-bundle to use JUnit 5 Key: NIFI-9112 URL: https://issues.apache.org/jira/browse/NIFI-9112 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9109) Refactor nifi-extension-utils to use JUnit 5
Mike Thomsen created NIFI-9109: -- Summary: Refactor nifi-extension-utils to use JUnit 5 Key: NIFI-9109 URL: https://issues.apache.org/jira/browse/NIFI-9109 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9105) Refactor nifi-easyrules-bundle to use JUnit 5
Mike Thomsen created NIFI-9105: -- Summary: Refactor nifi-easyrules-bundle to use JUnit 5 Key: NIFI-9105 URL: https://issues.apache.org/jira/browse/NIFI-9105 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9107) Refactor nifi-enrich-bundle to use JUnit 5
Mike Thomsen created NIFI-9107: -- Summary: Refactor nifi-enrich-bundle to use JUnit 5 Key: NIFI-9107 URL: https://issues.apache.org/jira/browse/NIFI-9107 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9108) Refactor nifi-evtx-bundle to use JUnit 5
Mike Thomsen created NIFI-9108: -- Summary: Refactor nifi-evtx-bundle to use JUnit 5 Key: NIFI-9108 URL: https://issues.apache.org/jira/browse/NIFI-9108 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9104) Refactor nifi-druid-bundle to use JUnit 5
Mike Thomsen created NIFI-9104: -- Summary: Refactor nifi-druid-bundle to use JUnit 5 Key: NIFI-9104 URL: https://issues.apache.org/jira/browse/NIFI-9104 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9106) Refactor nifi-email-bundle to use JUnit 5
Mike Thomsen created NIFI-9106: -- Summary: Refactor nifi-email-bundle to use JUnit 5 Key: NIFI-9106 URL: https://issues.apache.org/jira/browse/NIFI-9106 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9103) Refactor nifi-datadog-bundle to use JUnit 5
Mike Thomsen created NIFI-9103: -- Summary: Refactor nifi-datadog-bundle to use JUnit 5 Key: NIFI-9103 URL: https://issues.apache.org/jira/browse/NIFI-9103 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9110) Refactor nifi-flume-bundle to use JUnit 5
Mike Thomsen created NIFI-9110: -- Summary: Refactor nifi-flume-bundle to use JUnit 5 Key: NIFI-9110 URL: https://issues.apache.org/jira/browse/NIFI-9110 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9097) Refactor nifi-cassandra-bundle to use JUnit 5
Mike Thomsen created NIFI-9097: -- Summary: Refactor nifi-cassandra-bundle to use JUnit 5 Key: NIFI-9097 URL: https://issues.apache.org/jira/browse/NIFI-9097 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9102) Refactor nifi-cybersecurity-bundle to use JUnit 5
Mike Thomsen created NIFI-9102: -- Summary: Refactor nifi-cybersecurity-bundle to use JUnit 5 Key: NIFI-9102 URL: https://issues.apache.org/jira/browse/NIFI-9102 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9100) Refactor nifi-confluent-platform-bundle to use JUnit 5
Mike Thomsen created NIFI-9100: -- Summary: Refactor nifi-confluent-platform-bundle to use JUnit 5 Key: NIFI-9100 URL: https://issues.apache.org/jira/browse/NIFI-9100 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9098) Refactor nifi-ccda-bundle to use JUnit 5
Mike Thomsen created NIFI-9098: -- Summary: Refactor nifi-ccda-bundle to use JUnit 5 Key: NIFI-9098 URL: https://issues.apache.org/jira/browse/NIFI-9098 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9101) Refactor nifi-couchbase-bundle to use JUnit 5
Mike Thomsen created NIFI-9101: -- Summary: Refactor nifi-couchbase-bundle to use JUnit 5 Key: NIFI-9101 URL: https://issues.apache.org/jira/browse/NIFI-9101 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9096) Refactor nifi-beats-bundle to use JUnit 5
Mike Thomsen created NIFI-9096: -- Summary: Refactor nifi-beats-bundle to use JUnit 5 Key: NIFI-9096 URL: https://issues.apache.org/jira/browse/NIFI-9096 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9099) Refactor nifi-cdc-bundle to use JUnit 5
Mike Thomsen created NIFI-9099: -- Summary: Refactor nifi-cdc-bundle to use JUnit 5 Key: NIFI-9099 URL: https://issues.apache.org/jira/browse/NIFI-9099 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9095) Refactor nifi-azure-bundle to use JUnit 5
Mike Thomsen created NIFI-9095: -- Summary: Refactor nifi-azure-bundle to use JUnit 5 Key: NIFI-9095 URL: https://issues.apache.org/jira/browse/NIFI-9095 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9092) Refactor nifi-aws-bundle to use JUnit 5
Mike Thomsen created NIFI-9092: -- Summary: Refactor nifi-aws-bundle to use JUnit 5 Key: NIFI-9092 URL: https://issues.apache.org/jira/browse/NIFI-9092 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9091) Refactor nifi-avro-bundle to use JUnit 5
Mike Thomsen created NIFI-9091: -- Summary: Refactor nifi-avro-bundle to use JUnit 5 Key: NIFI-9091 URL: https://issues.apache.org/jira/browse/NIFI-9091 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9090) Refactor nifi-atlas-bundle to use JUnit 5
Mike Thomsen created NIFI-9090: -- Summary: Refactor nifi-atlas-bundle to use JUnit 5 Key: NIFI-9090 URL: https://issues.apache.org/jira/browse/NIFI-9090 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9089) Refactor nifi-asn1-bundle to use JUnit 5
Mike Thomsen created NIFI-9089: -- Summary: Refactor nifi-asn1-bundle to use JUnit 5 Key: NIFI-9089 URL: https://issues.apache.org/jira/browse/NIFI-9089 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9084) Refactor unit and integration tests to use JUnit 5 instead of JUnit 4
[ https://issues.apache.org/jira/browse/NIFI-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-9084: --- Description: This is the parent ticket to track all of this work. Everyone is welcome to attach a sub-task and take on a chunk of the work. Tickets for specific modules should be attached to this one and should only cover a handful of related modules to ensure that the work is scoped in a sane manner from the perspective of potential reviewers. (was: This is the parent ticket to track all of this work. Tickets for specific modules should be attached to this one and should only cover a handful of related modules to ensure that the work is scoped in a sane manner from the perspective of potential reviewers.) > Refactor unit and integration tests to use JUnit 5 instead of JUnit 4 > - > > Key: NIFI-9084 > URL: https://issues.apache.org/jira/browse/NIFI-9084 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Priority: Major > > This is the parent ticket to track all of this work. Everyone is welcome to > attach a sub-task and take on a chunk of the work. Tickets for specific > modules should be attached to this one and should only cover a handful of > related modules to ensure that the work is scoped in a sane manner from the > perspective of potential reviewers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9088) Refactor nifi-amqp-bundle to use JUnit 5
Mike Thomsen created NIFI-9088: -- Summary: Refactor nifi-amqp-bundle to use JUnit 5 Key: NIFI-9088 URL: https://issues.apache.org/jira/browse/NIFI-9088 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-9087) Refactor nifi-ambari-bundle to use JUnit 5
[ https://issues.apache.org/jira/browse/NIFI-9087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen reassigned NIFI-9087: -- Assignee: Mike Thomsen > Refactor nifi-ambari-bundle to use JUnit 5 > -- > > Key: NIFI-9087 > URL: https://issues.apache.org/jira/browse/NIFI-9087 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9087) Refactor nifi-ambari-bundle to use JUnit 5
Mike Thomsen created NIFI-9087: -- Summary: Refactor nifi-ambari-bundle to use JUnit 5 Key: NIFI-9087 URL: https://issues.apache.org/jira/browse/NIFI-9087 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9087) Refactor nifi-ambari-bundle to use JUnit 5
[ https://issues.apache.org/jira/browse/NIFI-9087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-9087: --- Priority: Minor (was: Major) > Refactor nifi-ambari-bundle to use JUnit 5 > -- > > Key: NIFI-9087 > URL: https://issues.apache.org/jira/browse/NIFI-9087 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-9085) Refactor nifi-elasticsearch-bundle to use JUnit 5 for test cases
[ https://issues.apache.org/jira/browse/NIFI-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-9085: --- Summary: Refactor nifi-elasticsearch-bundle to use JUnit 5 for test cases (was: Refactor the Elasticsearch bundle to use JUnit 5 for test cases) > Refactor nifi-elasticsearch-bundle to use JUnit 5 for test cases > > > Key: NIFI-9085 > URL: https://issues.apache.org/jira/browse/NIFI-9085 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9086) Refactor nifi-accumulo-bundle to use JUnit 5
Mike Thomsen created NIFI-9086: -- Summary: Refactor nifi-accumulo-bundle to use JUnit 5 Key: NIFI-9086 URL: https://issues.apache.org/jira/browse/NIFI-9086 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9085) Refactor the Elasticsearch bundle to use JUnit 5 for test cases
Mike Thomsen created NIFI-9085: -- Summary: Refactor the Elasticsearch bundle to use JUnit 5 for test cases Key: NIFI-9085 URL: https://issues.apache.org/jira/browse/NIFI-9085 Project: Apache NiFi Issue Type: Sub-task Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9084) Refactor unit and integration tests to use JUnit 5 instead of JUnit 4
Mike Thomsen created NIFI-9084: -- Summary: Refactor unit and integration tests to use JUnit 5 instead of JUnit 4 Key: NIFI-9084 URL: https://issues.apache.org/jira/browse/NIFI-9084 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen This is the parent ticket to track all of this work. Tickets for specific modules should be attached to this one and should only cover a handful of related modules to ensure that the work is scoped in a sane manner from the perspective of potential reviewers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9081) Convert nifi-api, nifi-external, nifi-framework-api and nifi-stateless to use JUnit 5
Mike Thomsen created NIFI-9081: -- Summary: Convert nifi-api, nifi-external, nifi-framework-api and nifi-stateless to use JUnit 5 Key: NIFI-9081 URL: https://issues.apache.org/jira/browse/NIFI-9081 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen Assignee: Mike Thomsen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9080) Convert nifi-commons to use all JUnit 5 APIs
Mike Thomsen created NIFI-9080: -- Summary: Convert nifi-commons to use all JUnit 5 APIs Key: NIFI-9080 URL: https://issues.apache.org/jira/browse/NIFI-9080 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen Assignee: Mike Thomsen Remove all references to JUnit 4 APIs and replace them with the appropriate JUnit 5 APIs and conventions in nifi-commons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-9041) Enable the current JUnit tests to run on top of JUnit 5
[ https://issues.apache.org/jira/browse/NIFI-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398012#comment-17398012 ] Mike Thomsen commented on NIFI-9041: [~exceptionfactory] [https://github.com/apache/nifi/pull/5304] if you have time. > Enable the current JUnit tests to run on top of JUnit 5 > --- > > Key: NIFI-9041 > URL: https://issues.apache.org/jira/browse/NIFI-9041 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The goal of this effort will be to refactor the code base so that we are > running everything with the Jupiter execution engine with JUnit 4 legacy > support. Once this work is in place, follow on tickets will be added to > convert the code base module by module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-9041) Enable the current JUnit tests to run on top of JUnit 5
Mike Thomsen created NIFI-9041: -- Summary: Enable the current JUnit tests to run on top of JUnit 5 Key: NIFI-9041 URL: https://issues.apache.org/jira/browse/NIFI-9041 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen Assignee: Mike Thomsen The goal of this effort will be to refactor the code base so that we are running everything with the Jupiter execution engine with JUnit 4 legacy support. Once this work is in place, follow on tickets will be added to convert the code base module by module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-9024) Upgrade from JUnit 4 to JUnit 5 Jupiter
[ https://issues.apache.org/jira/browse/NIFI-9024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397665#comment-17397665 ] Mike Thomsen commented on NIFI-9024: Given how large and diverse our code base is, I think a lot of the early work would have to be done by hand. [~jschneider] I actually got started on making some of those changes by hand. I would suggest we split the work so that we have everything running on the Jupiter Engine w/ backward compatibility for 4.X and then start a module-by-module conversion. > Upgrade from JUnit 4 to JUnit 5 Jupiter > --- > > Key: NIFI-9024 > URL: https://issues.apache.org/jira/browse/NIFI-9024 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Jonathan K. Schneider >Priority: Major > Attachments: nifi.jpg > > > Hi! I'm an author on [OpenRewrite|[https://github.com/openrewrite/rewrite],] > an open source automated refactoring engine. I'd like to help do the work to > move NIFI to JUnit 5 Jupiter from JUnit 4. We've done this on several other > projects as well. Below is a sampling of a test migration on part of NIFI's > code. Could we time the issuance of a PR with a NIFI maintainer's schedule to > make this change? > !nifi.jpg! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (NIFI-9023) Upgrade from JUnit 4 to JUnit 5 Jupiter
[ https://issues.apache.org/jira/browse/NIFI-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen closed NIFI-9023. -- > Upgrade from JUnit 4 to JUnit 5 Jupiter > --- > > Key: NIFI-9023 > URL: https://issues.apache.org/jira/browse/NIFI-9023 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Jonathan K. Schneider >Priority: Major > > Hi! I'm an author on [OpenRewrite|[https://github.com/openrewrite/rewrite],] > an open source automated refactoring engine. I'd like to help do the work to > move NIFI to JUnit 5 Jupiter from JUnit 4. We've done this on several other > projects as well. Below is a sampling of a test migration on part of NIFI's > code. Could we time the issuance of a PR with a NIFI maintainer's schedule to > make this change? > !https://ton.twitter.com/1.1/ton/data/dm/1424077819085156358/1424077666865451012/v9b9-qgP.jpg:large! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-5936) MockProcessSession remove() does not report a "DROP" provenance event
[ https://issues.apache.org/jira/browse/NIFI-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-5936: --- Fix Version/s: 1.15.0 Resolution: Fixed Status: Resolved (was: Patch Available) > MockProcessSession remove() does not report a "DROP" provenance event > - > > Key: NIFI-5936 > URL: https://issues.apache.org/jira/browse/NIFI-5936 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Joe Percivall >Assignee: Matt Burgess >Priority: Minor > Fix For: 1.15.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The StandardProcessSession remove method emits a "DROPPED" provenance > event[1] whereas the MockProcessSession does not[2]. MockProcessSession > should mimic the Standard as closely as possible. > [1] > https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java#L2002 > [2] > https://github.com/apache/nifi/blob/master/nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java#L620 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-8209) The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs indefinitely attempting to connect to Neo4j 4.2.3
[
https://issues.apache.org/jira/browse/NIFI-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396841#comment-17396841
]
Mike Thomsen commented on NIFI-8209:
[~fburgess] I'm in the process of (hopefully) finishing up a PR that addresses
your issues.
> The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs
> indefinitely attempting to connect to Neo4j 4.2.3
> --
>
> Key: NIFI-8209
> URL: https://issues.apache.org/jira/browse/NIFI-8209
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions, Tools and Build
>Affects Versions: 1.12.1
> Environment: UNIX/CentOS 7
>Reporter: freddie Burgess
>Assignee: Mike Thomsen
>Priority: Major
>
> The latest Neo4j Controller Service in Nifi from the graph bundle has been
> built using neo4j-java-driver v1.6.2 and is not compatible with Neo4j 4.x.
> Enabling the controller fails in reaching the Neo4j database.
> neo4j-enterprise-edition
> Nifi 1.11.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
> neo4j-community-edition
> Nifi 1.12.x + Neo 4.2.3 => ServiceUnavailableException
> Nifi 1.12.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
>
> 2021-01-13 20:00:02,167 ERROR [Timer-Driven Process Thread-9]
> o.a.n.c.s.StandardControllerServiceNode
> StandardControllerServiceNode[service=Neo4JCypherClientService[id=192a1810-11da-101d-b4cd-f704063cba3d],
> versionedComponentId=null,
> processGroup=StandardProcessGroup[identifier=6038b1ce-016d-1000-68fc-0a8f542cf79b,name=NiFi
> Flow], active=true] Failed to invoke @OnEnabled method due to
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database: {}
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database
> at
> org.apache.nifi.graph.Neo4JCypherClientService.onEnabled(Neo4JCypherClientService.java:255)
> at jdk.internal.reflect.GeneratedMethodAccessor505.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:142)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:130)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:75)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:52)
> at
> org.apache.nifi.controller.service.StandardControllerServiceNode$2.run(StandardControllerServiceNode.java:432)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.neo4j.driver.v1.exceptions.ServiceUnavailableException:
> Connection to the database terminated. This can happen due to network
> instabilities, or due to restarts of the database
> at
> org.neo4j.driver.internal.util.ErrorUtil.newConnectionTerminatedError(ErrorUtil.java:45)
> at
> org.neo4j.driver.internal.async.HandshakeHandler.channelInactive(HandshakeHandler.java:85)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
> at
>
[jira] [Commented] (NIFI-8209) The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs indefinitely attempting to connect to Neo4j 4.2.3
[
https://issues.apache.org/jira/browse/NIFI-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395277#comment-17395277
]
Mike Thomsen commented on NIFI-8209:
[~mattyb149] I think the right solution here would be to update main cypher
client and then create a new legacy NAR for 3.X support. Thoughts?
> The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs
> indefinitely attempting to connect to Neo4j 4.2.3
> --
>
> Key: NIFI-8209
> URL: https://issues.apache.org/jira/browse/NIFI-8209
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions, Tools and Build
>Affects Versions: 1.12.1
> Environment: UNIX/CentOS 7
>Reporter: freddie Burgess
>Assignee: Mike Thomsen
>Priority: Major
>
> The latest Neo4j Controller Service in Nifi from the graph bundle has been
> built using neo4j-java-driver v1.6.2 and is not compatible with Neo4j 4.x.
> Enabling the controller fails in reaching the Neo4j database.
> neo4j-enterprise-edition
> Nifi 1.11.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
> neo4j-community-edition
> Nifi 1.12.x + Neo 4.2.3 => ServiceUnavailableException
> Nifi 1.12.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
>
> 2021-01-13 20:00:02,167 ERROR [Timer-Driven Process Thread-9]
> o.a.n.c.s.StandardControllerServiceNode
> StandardControllerServiceNode[service=Neo4JCypherClientService[id=192a1810-11da-101d-b4cd-f704063cba3d],
> versionedComponentId=null,
> processGroup=StandardProcessGroup[identifier=6038b1ce-016d-1000-68fc-0a8f542cf79b,name=NiFi
> Flow], active=true] Failed to invoke @OnEnabled method due to
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database: {}
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database
> at
> org.apache.nifi.graph.Neo4JCypherClientService.onEnabled(Neo4JCypherClientService.java:255)
> at jdk.internal.reflect.GeneratedMethodAccessor505.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:142)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:130)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:75)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:52)
> at
> org.apache.nifi.controller.service.StandardControllerServiceNode$2.run(StandardControllerServiceNode.java:432)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.neo4j.driver.v1.exceptions.ServiceUnavailableException:
> Connection to the database terminated. This can happen due to network
> instabilities, or due to restarts of the database
> at
> org.neo4j.driver.internal.util.ErrorUtil.newConnectionTerminatedError(ErrorUtil.java:45)
> at
> org.neo4j.driver.internal.async.HandshakeHandler.channelInactive(HandshakeHandler.java:85)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
> at
>
[jira] [Assigned] (NIFI-8209) The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs indefinitely attempting to connect to Neo4j 4.2.3
[
https://issues.apache.org/jira/browse/NIFI-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen reassigned NIFI-8209:
--
Assignee: Mike Thomsen
> The Apache Nifi 1.12.1 Neo4JCypherClientService controller service hangs
> indefinitely attempting to connect to Neo4j 4.2.3
> --
>
> Key: NIFI-8209
> URL: https://issues.apache.org/jira/browse/NIFI-8209
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions, Tools and Build
>Affects Versions: 1.12.1
> Environment: UNIX/CentOS 7
>Reporter: freddie Burgess
>Assignee: Mike Thomsen
>Priority: Major
>
> The latest Neo4j Controller Service in Nifi from the graph bundle has been
> built using neo4j-java-driver v1.6.2 and is not compatible with Neo4j 4.x.
> Enabling the controller fails in reaching the Neo4j database.
> neo4j-enterprise-edition
> Nifi 1.11.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
> neo4j-community-edition
> Nifi 1.12.x + Neo 4.2.3 => ServiceUnavailableException
> Nifi 1.12.x + Neo 4.2.2 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.1.5 => ServiceUnavailableException
> Nifi 1.11.x + Neo 4.0.11 => ServiceUnavailableException
> Nifi 1.11.x + Neo 3.5.26 => OK
>
> 2021-01-13 20:00:02,167 ERROR [Timer-Driven Process Thread-9]
> o.a.n.c.s.StandardControllerServiceNode
> StandardControllerServiceNode[service=Neo4JCypherClientService[id=192a1810-11da-101d-b4cd-f704063cba3d],
> versionedComponentId=null,
> processGroup=StandardProcessGroup[identifier=6038b1ce-016d-1000-68fc-0a8f542cf79b,name=NiFi
> Flow], active=true] Failed to invoke @OnEnabled method due to
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database: {}
> org.apache.nifi.processor.exception.ProcessException: Error while getting
> connectionConnection to the database terminated. This can happen due to
> network instabilities, or due to restarts of the database
> at
> org.apache.nifi.graph.Neo4JCypherClientService.onEnabled(Neo4JCypherClientService.java:255)
> at jdk.internal.reflect.GeneratedMethodAccessor505.invoke(Unknown Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:142)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:130)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:75)
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:52)
> at
> org.apache.nifi.controller.service.StandardControllerServiceNode$2.run(StandardControllerServiceNode.java:432)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.neo4j.driver.v1.exceptions.ServiceUnavailableException:
> Connection to the database terminated. This can happen due to network
> instabilities, or due to restarts of the database
> at
> org.neo4j.driver.internal.util.ErrorUtil.newConnectionTerminatedError(ErrorUtil.java:45)
> at
> org.neo4j.driver.internal.async.HandshakeHandler.channelInactive(HandshakeHandler.java:85)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:245)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:231)
> at
> org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:224)
> at
> org.neo4j.driver.internal.shaded.io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:377)
> at
>
[jira] [Created] (NIFI-9022) Add a simple MergeJson processor to facilitate simple merge scenarios
Mike Thomsen created NIFI-9022: -- Summary: Add a simple MergeJson processor to facilitate simple merge scenarios Key: NIFI-9022 URL: https://issues.apache.org/jira/browse/NIFI-9022 Project: Apache NiFi Issue Type: New Feature Reporter: Mike Thomsen Assignee: Mike Thomsen The goal of this processor is to provide something simpler than MergeRecord for merging JSON content. It generates an array of JSON output in a single flowfile. We've run into this problem on numerous occasions where a team would give us JSON that is either schema-less or whose schema is too dynamic for MergeRecord. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-9013) Eliminate unnecessary dependency from nifi-data-provenance-utils on nifi-properties & loader
[ https://issues.apache.org/jira/browse/NIFI-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-9013. Fix Version/s: 1.15.0 Resolution: Fixed > Eliminate unnecessary dependency from nifi-data-provenance-utils on > nifi-properties & loader > > > Key: NIFI-9013 > URL: https://issues.apache.org/jira/browse/NIFI-9013 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, NiFi Stateless >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 1.15.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The nifi-data-provenance-utils has a maven dependency on nifi-properties and > nifi-properties-loader but does not use them. Perhaps this was due to a > refactoring. > This dependency, though, adds about 10 MB of extra dependencies to > nifi-stateless, which means that it bloats the nifi-stateless assembly by > 25%. We should be able to simply remove the maven dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8993) Add the ability to connect directly to a SchemaRegistry service from within ScriptedTransformRecord to enable the conversion of records
Mike Thomsen created NIFI-8993: -- Summary: Add the ability to connect directly to a SchemaRegistry service from within ScriptedTransformRecord to enable the conversion of records Key: NIFI-8993 URL: https://issues.apache.org/jira/browse/NIFI-8993 Project: Apache NiFi Issue Type: New Feature Reporter: Mike Thomsen Assignee: Mike Thomsen The ScriptedTransformRecord processor has the ability to be used as a programmatic alternative to JOLT. I've done this before with it using a fat jar that contains a compiled version of an Avro schema, imported a helper class that defines the schema, and then used the processor to generate and write new records. It's a really powerful and easy to debug alternative to anything that uses JOLT. The purpose of this ticket is to enable users to bypass the the creation of a fat jar and directly access a schema registry with a helper that simplifies the lookup process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8152) Fix NPE in RedisDistributedMapCacheClientService caused by newer versions of Jedis
[ https://issues.apache.org/jira/browse/NIFI-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-8152. Fix Version/s: 1.14.0 Resolution: Fixed > Fix NPE in RedisDistributedMapCacheClientService caused by newer versions of > Jedis > -- > > Key: NIFI-8152 > URL: https://issues.apache.org/jira/browse/NIFI-8152 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.12.1 > Environment: Custom Docker Image with OpenJDK 11, based on Debian > Host: Debian Buster >Reporter: Bernhard Geisberger >Priority: Minor > Fix For: 1.14.0 > > > Update: > I've found out that RedisDistributedMapCacheClientService is not compatible > with newer versions of jedis. In particular, this change is breaking: > https://github.com/redis/jedis/pull/1368 > This is included in all versions after 2.9.0. (including bugfix versions > 2.9.1+) > To ensure compatibility with newer jedis versions in the (global) classpath > (which is unfortunately the only way to go sometimes), a null response from > redis should be treated the same as an empty list. > Original issue text: > Since our upgrade to NiFi 1.12.1 (we ran 1.8 before), DetectDuplicate throws > some rare NullPointerExceptions. It is not reproducible directly with the > same flowfiles again. > The stacktrace shows that it is caused by > RedisDistributedMapCacheClientService, line 165, where the results of > redisConnection.exec() are checked. > Looking at the source code of spring-data-redis, it is actually possible that > the exec() call returns null in some error cases, as you can see here: > https://github.com/spring-projects/spring-data-redis/blob/master/src/main/java/org/springframework/data/redis/connection/jedis/JedisConnection.java#L482 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8411) Update github CI usage to latest java action for distribution control
[ https://issues.apache.org/jira/browse/NIFI-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-8411. Fix Version/s: 1.14.0 Resolution: Fixed > Update github CI usage to latest java action for distribution control > - > > Key: NIFI-8411 > URL: https://issues.apache.org/jira/browse/NIFI-8411 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Switch to > https://github.com/actions/setup-java/blob/main/docs/switching-to-v2.md > And investigate how to explicitly set maven version until we figure out how > to ensure all repos we interact with are done so under https exclusively. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8374) ApiModelProperty readOnly is deprecated
[
https://issues.apache.org/jira/browse/NIFI-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-8374.
Fix Version/s: 1.14.0
Resolution: Fixed
> ApiModelProperty readOnly is deprecated
> ---
>
> Key: NIFI-8374
> URL: https://issues.apache.org/jira/browse/NIFI-8374
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Jose Luis Pedrosa
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Swagger io.swagger.annotations.ApiModelProperty#readOnly is deprecated
> (1.5.19), replaced by accessMode()
> So the annotations:
> {code:java}
> readOnly = true
> {code}
> should be replaced with
> {code:java}
> accessMode = ApiModelProperty.AccessMode.READ_ONLY
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-8374) ApiModelProperty readOnly is deprecated
[
https://issues.apache.org/jira/browse/NIFI-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen updated NIFI-8374:
---
Priority: Minor (was: Major)
> ApiModelProperty readOnly is deprecated
> ---
>
> Key: NIFI-8374
> URL: https://issues.apache.org/jira/browse/NIFI-8374
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 1.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Swagger io.swagger.annotations.ApiModelProperty#readOnly is deprecated
> (1.5.19), replaced by accessMode()
> So the annotations:
> {code:java}
> readOnly = true
> {code}
> should be replaced with
> {code:java}
> accessMode = ApiModelProperty.AccessMode.READ_ONLY
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFI-4307) Add Kotlin support to ExecuteScript
[ https://issues.apache.org/jira/browse/NIFI-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17294717#comment-17294717 ] Mike Thomsen commented on NIFI-4307: After what you said about the REPL, I'm not even sure there is a sane way to do this. Maybe we should close it down and put a release note out explaining why. Thoughts on that? > Add Kotlin support to ExecuteScript > --- > > Key: NIFI-4307 > URL: https://issues.apache.org/jira/browse/NIFI-4307 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Minor > > Kotlin has a ScriptEngine implementation as of v1.1. Add support for it in > NiFi. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8156) PutCassandraRecord does not wrap byte arrays with a ByteBuffer, causing write failures
Mike Thomsen created NIFI-8156: -- Summary: PutCassandraRecord does not wrap byte arrays with a ByteBuffer, causing write failures Key: NIFI-8156 URL: https://issues.apache.org/jira/browse/NIFI-8156 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.12.1 Reporter: Mike Thomsen Assignee: Mike Thomsen As the subject line says, types that are meant for a Cassandra bytes field are not wrapped inside of a ByteBuffer. This causes a write failure when the Cassandra driver attempts to write the array. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8074) Change the default behavior of ReplaceText to use line by line evaluation
[ https://issues.apache.org/jira/browse/NIFI-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-8074. Fix Version/s: 1.13.0 Resolution: Fixed > Change the default behavior of ReplaceText to use line by line evaluation > - > > Key: NIFI-8074 > URL: https://issues.apache.org/jira/browse/NIFI-8074 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Major > Fix For: 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > I've seen a lot of users report out of memory errors with ReplaceText because > they didn't realize that line by line evaluation was possible. I think > changing the default to line by line will make things a lot easier for the > vast majority of casual users who may not look too deeply into the > configuration options -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8080) Apply ScriptedTransformRecord approach to Jython for other scripted components
[ https://issues.apache.org/jira/browse/NIFI-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-8080. Resolution: Fixed > Apply ScriptedTransformRecord approach to Jython for other scripted components > -- > > Key: NIFI-8080 > URL: https://issues.apache.org/jira/browse/NIFI-8080 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h > Remaining Estimate: 0h > > ScriptedTransformRecord (NIFI-7572) has code specifically for Jython (since > it implements the Compilable interface) to compile the script first, > resulting in up to 10x performance improvements. The same can be done for > JythonScriptEngineConfigurator so all other scripted components can make use > of those improvements. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-8080) Apply ScriptedTransformRecord approach to Jython for other scripted components
[ https://issues.apache.org/jira/browse/NIFI-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-8080. Fix Version/s: 1.13.0 Resolution: Fixed > Apply ScriptedTransformRecord approach to Jython for other scripted components > -- > > Key: NIFI-8080 > URL: https://issues.apache.org/jira/browse/NIFI-8080 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > ScriptedTransformRecord (NIFI-7572) has code specifically for Jython (since > it implements the Compilable interface) to compile the script first, > resulting in up to 10x performance improvements. The same can be done for > JythonScriptEngineConfigurator so all other scripted components can make use > of those improvements. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8031) Support MySQL Upsert in PutDatabaseRecord
[ https://issues.apache.org/jira/browse/NIFI-8031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-8031: --- Fix Version/s: 1.13.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Support MySQL Upsert in PutDatabaseRecord > - > > Key: NIFI-8031 > URL: https://issues.apache.org/jira/browse/NIFI-8031 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Related to NIFI-6934 which put in the plumbing and initial implementation of > an UPSERT capability for PostgreSQL, this Jira proposes to add support for > UPSERT in MySQL using the "INSERT with ON DUPLICATE KEY UPDATE" syntax. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8074) Change the default behavior of ReplaceText to use line by line evaluation
Mike Thomsen created NIFI-8074: -- Summary: Change the default behavior of ReplaceText to use line by line evaluation Key: NIFI-8074 URL: https://issues.apache.org/jira/browse/NIFI-8074 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen Assignee: Mike Thomsen I've seen a lot of users report out of memory errors with ReplaceText because they didn't realize that line by line evaluation was possible. I think changing the default to line by line will make things a lot easier for the vast majority of casual users who may not look too deeply into the configuration options -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6878) ConvertJSONToSQL Improvement. Statement Type Support "Use statement.type Attribute" or Supports Expression Language
[ https://issues.apache.org/jira/browse/NIFI-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-6878: --- Fix Version/s: 1.13.0 Resolution: Fixed Status: Resolved (was: Patch Available) > ConvertJSONToSQL Improvement. Statement Type Support "Use statement.type > Attribute" or Supports Expression Language > - > > Key: NIFI-6878 > URL: https://issues.apache.org/jira/browse/NIFI-6878 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: ZhangCheng >Assignee: Matt Burgess >Priority: Minor > Fix For: 1.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > ConvertJSONToSQL Statement Type provides fixed options : > UPDATE,INSERT,DELETE. > Usually, it can meet our needs. But in actual application,I think It's not > flexible enough. > In some cases, we need to dynamically indicate the Statement Type. > For example,the data from CpatureChangeMysql owns the attribute of > statement type（cdc.event.type, we need to convert the data to sql(DML) > orderly; And we now have to use RouteOnAttribute to transfer data to three > branches , Build SQL statement separately ,finally,we have to use > EnforceOrder to ensure the order of SQL statements. > But it will be easy if ConvertJSONToSQL supports dynamical Statement Type . > It is easy to implement this feature just like PutDatabaseRecord. > In practice, I did use PutDatabaseRecord instead of ConvertJSONToSQL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8042) ReplaceText failing to update text when using Literal Replacement Strategy with Expression Language
[
https://issues.apache.org/jira/browse/NIFI-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen updated NIFI-8042:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ReplaceText failing to update text when using Literal Replacement Strategy
> with Expression Language
> ---
>
> Key: NIFI-8042
> URL: https://issues.apache.org/jira/browse/NIFI-8042
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> From mailing list:
> I've successfully tested Variable Registries in the *Replacement Value*
> field, but I still can't get it to work in the *Search Value* field with
> *Replacement Strategy* as Literal Replace and *Evaluation* as Entire Text.
>
> Here is something really weird. I created a GenerateFlowFile and used my
> ${tier1.linux} variable in the *Custom Text* field. Creates the flow file as
> expected, with the expected text. But then in my ReplaceText's *Search Value*
> field I use my ${tier1.linux} variable with *Replacement* being anything, and
> it +does not+ ** successfully search and replace the text. Thoughts?
>
> *GenerateFlowFile Values*
> File Size: 0B
> Batch Size: 1
> Data Format: Text (granted, I'm using JSON in my official version, but it
> should still work)
> Unique FlowFiles: false
> Custom Text: ${tier1.linux}
> Character Set: UTF-8
> Mime Type: No value set
>
> *ReplaceText Values*
> Search Value: ${tier1.linux}
> Replacement Value: hello world
> Character Set: UTF-8
> Max Buff Size: 1MB (way more than I need)
> Replacement Strat: Literal Replace
> Evaluation Mode: Entire Text
> Line-b-Line: All
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-7260) Scripted controller services do not handle Module Directory changes or script errors properly
[ https://issues.apache.org/jira/browse/NIFI-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-7260: --- Fix Version/s: 1.13.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Scripted controller services do not handle Module Directory changes or script > errors properly > - > > Key: NIFI-7260 > URL: https://issues.apache.org/jira/browse/NIFI-7260 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently for all scripted controller services (ScriptedReader, e.g.) the > scripting engine (with additional classpath modules defined by the Module > Directory property) is only recreated when the Script Engine property has > changed. It should be recreated when the Module Directory property has > changed as well. > In addition, the controller service can be enabled even with an error in the > script. The controller service reports internally that it is invalid, but > becomes enabled anyway, hiding the invalid status from the user. They may > also suffer from the issue in NIFI-4968 with logging while the script is > invalid. Instead an exception should be thrown, which prevents the CS from > being enabled, then the fix from NIFI-4968 should be applied so that > excessive logging does not occur while the CS is invalid. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-8032) fix RecordPath Guide doc
[ https://issues.apache.org/jira/browse/NIFI-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-8032: --- Fix Version/s: 1.13.0 Resolution: Fixed Status: Resolved (was: Patch Available) > fix RecordPath Guide doc > > > Key: NIFI-8032 > URL: https://issues.apache.org/jira/browse/NIFI-8032 > Project: Apache NiFi > Issue Type: Bug >Reporter: ZhangCheng >Assignee: ZhangCheng >Priority: Major > Fix For: 1.13.0 > > Attachments: image-2020-11-20-15-01-25-617.png, > image-2020-11-20-15-02-02-666.png > > Time Spent: 20m > Remaining Estimate: 0h > > !image-2020-11-20-15-01-25-617.png! > > !image-2020-11-20-15-02-02-666.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-7982) Add Run Duration option to FlattanJSON processor
[ https://issues.apache.org/jira/browse/NIFI-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-7982. Fix Version/s: 1.13.0 Resolution: Fixed > Add Run Duration option to FlattanJSON processor > > > Key: NIFI-7982 > URL: https://issues.apache.org/jira/browse/NIFI-7982 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Rahul Soni >Assignee: r65535 >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > FlattenJSON processor doesn't have a run duration today. As a result, the > flows using it sometimes needs to assign more threads to the processor for a > higher throughput, which is not an ideal scenario. In order to yield maximum > throughput from FlattenJSON processor, I would propose adding Run Duration > option to the scheduling section. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-7891) Allow for Defaults to be set by Avro writers
[
https://issues.apache.org/jira/browse/NIFI-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-7891.
Resolution: Won't Do
As mentioned on GitHub, the contribution is appreciated, but we have to pass
because it would introduce a lot of potentially disruptive behavior to users of
schema inference.
> Allow for Defaults to be set by Avro writers
>
>
> Key: NIFI-7891
> URL: https://issues.apache.org/jira/browse/NIFI-7891
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Alasdair Brown
>Assignee: Alasdair Brown
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This would be an improvement to Avro writer services. Allowing a set of
> default values to be given based on the data type when infering the schema.
>
> For example, you could have an additional property per type (e.g. Int,
> String, etc.) where the value of the property would be used as the default
> value. However, this would add a lot of properties Possibly you could
> provide a JSON set of types -> defaults, e.g.
> {code:java}
> [
>{ "type":"string", "default":"test"},
>{ "type":"int","default":1},
> ]{code}
> Thus, for any field inferred as type String, it's embedded Avro schema
> contains a default value entry for that field.
> This would then provide flexibility where NULL values are present - the
> current behaviour only supports adding NULL to the allowable types - this
> would be a very useful alternative.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-7981) ConvertRecord cannot handle open enum in Avro
[
https://issues.apache.org/jira/browse/NIFI-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen updated NIFI-7981:
---
Fix Version/s: 1.13.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ConvertRecord cannot handle open enum in Avro
> -
>
> Key: NIFI-7981
> URL: https://issues.apache.org/jira/browse/NIFI-7981
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.12.1
>Reporter: Christophe Monnet
>Assignee: Pierre Villard
>Priority: Minor
> Fix For: 1.13.0
>
> Attachments: record_enum.xml
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> This avro schema is using the open enum pattern:
> {code:json}
> {
> "namespace": "acme",
> "name": "openEnum",
> "type": "record",
> "fields": [{
> "name": "personType",
> "type": ["null", {
> "type": "enum",
> "name": "personType_enum",
> "symbols": [
> "DRIVER",
> "TECHNICIAN"
> ]
> }, "string"],
> "default": null
> }
> ]
> }
> {code}
> The *personType* can be either null, an enum, or any string. This brings
> forward-compatibility.
> Using ConvertRecord with
> {"personType":"DRIVER"}
> as a payload, it works.
> But with
> {"personType":"DUDE"}
> it fails with {{java.lang.NullPointerException: null of acme.personType_enum
> of union in field personType of acme.openEnum}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (NIFI-7978) Update macOS Homebrew documentation
[ https://issues.apache.org/jira/browse/NIFI-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-7978. Fix Version/s: 1.13.0 Resolution: Fixed > Update macOS Homebrew documentation > --- > > Key: NIFI-7978 > URL: https://issues.apache.org/jira/browse/NIFI-7978 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.12.1 >Reporter: Dustin Rodrigues >Assignee: Dustin Rodrigues >Priority: Minor > Fix For: 1.13.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Getting Started documentation has a recommendation to install Java > outside of Homebrew since the Homebrew formula didn't previously depend on a > specific Java version. The current formula now explicitly depends on OpenJDK > 11 so this recommendation is no longer needed: > https://github.com/Homebrew/homebrew-core/pull/63998. If a user has a > different version of Java installed with the corresponding JAVA_HOME set, > that Java will be used instead if the person doesn't want to use OpenJDK 11 > from Homebrew. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-5226) Implement a Record API based PutInfluxDB processor
[ https://issues.apache.org/jira/browse/NIFI-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-5226: --- Resolution: Won't Do Status: Resolved (was: Patch Available) The contributor moved it to a separate repo which can be found here: [https://github.com/influxdata/nifi-influxdb-bundle] > Implement a Record API based PutInfluxDB processor > -- > > Key: NIFI-5226 > URL: https://issues.apache.org/jira/browse/NIFI-5226 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Bonitoo4Influxdata Engineering >Priority: Major > Labels: influx, processor, timeseries > Time Spent: 2h > Remaining Estimate: 0h > > Implement a new processor that uses the Record API to put data into InfluxDB. > PutInfluxDBRecord features: > * Input can be any built-in or custom implemented NiFi RecordReader (json, > avro, csv, InfluxLineProtocolReader...) > * Configurable mapping between NiFi Records and InfluxDB measurement, field > and tags > * Configurable timestamp precision > * Reusable connection settings (InfluxDB url, password) for more processors > via InfluxDBService controller > * Advanced InfluxDB client settings > * > ** Gzip compression > ** Batching, jitter, flush settings > InfluxDBService features: > * InfluxDBService allows sharing connection configuration among more NiFi > processors. > * SSL support > InfluxLineProtocolReader features > * InfluxLineProtocolReader parses the InfluxDB Line Protocol into NiFi > Record. This allows processing, filtering and partitioning data in NiFi > obtained from Telegraf agents, IoT devices, InfluxDB subscriptions and other > InfluxDB Line protocol devices. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-385) Add Kerberos support in nifi-kite-nar
[
https://issues.apache.org/jira/browse/NIFI-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-385.
---
Resolution: Won't Do
Based on these update dates, Kite appears to be abandoned.
https://search.maven.org/search?q=g:org.kitesdk
> Add Kerberos support in nifi-kite-nar
> -
>
> Key: NIFI-385
> URL: https://issues.apache.org/jira/browse/NIFI-385
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Ryan Blue
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Kite should be able to connect to a Kerberized Hadoop cluster to store data.
> Kite's Flume connector has working code. The Kite dataset needs to be
> instantiated in a {{doPrivileged}} block and its internal {{FileSystem}}
> object will hold the credentials after that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (NIFI-5407) Add a MetricsReportingTask to send to ElasticSearch
[ https://issues.apache.org/jira/browse/NIFI-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-5407. Resolution: Won't Do > Add a MetricsReportingTask to send to ElasticSearch > --- > > Key: NIFI-5407 > URL: https://issues.apache.org/jira/browse/NIFI-5407 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.7.0 >Reporter: rich >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > > As far as I can tell, there isn't a MetricsReportingTask which persists to > Elastic. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-3518) Create a Morphlines processor
[ https://issues.apache.org/jira/browse/NIFI-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen resolved NIFI-3518. Resolution: Won't Do Morphline appears to be abandoned now, so I'm closing this out. > Create a Morphlines processor > - > > Key: NIFI-3518 > URL: https://issues.apache.org/jira/browse/NIFI-3518 > Project: Apache NiFi > Issue Type: New Feature >Reporter: William Nouet >Priority: Minor > Attachments: NIFI-3518-versionupdates.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Create a dedicate processor to run Morphlines transformations > (http://kitesdk.org/docs/1.1.0/morphlines/morphlines-reference-guide.html) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-1395) Some tests fail on Windows because of expected LF line endings
[
https://issues.apache.org/jira/browse/NIFI-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-1395.
Resolution: Fixed
We have GitHub CI/CD builds on Windows now passing just fine, so apparently
this got fixed some time ago.
> Some tests fail on Windows because of expected LF line endings
> --
>
> Key: NIFI-1395
> URL: https://issues.apache.org/jira/browse/NIFI-1395
> Project: Apache NiFi
> Issue Type: Bug
> Environment: Windows 10 64bit
> Java 1.8.0_66
>Reporter: Thad Guidry
>Priority: Major
>
> The test Original.txt files have UNIX Linefeeds (ascii char 10), but when the
> tests are run on Windows, the FlowFile created will have DOS format Carriage
> Returns (ascii char 13).
> {quote}
> Running org.apache.nifi.processors.standard.TestConvertCharacterSet
> Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.163 sec <<<
> FAILURE! - in org.apache.nifi.processors.standard.TestConvertCharacterSet
> testExpressionLanguageOutput(org.apache.nifi.processors.standard.TestConvertCharacterSet)
> Time elapsed: 0.025 sec <<< FAILURE!
> java.lang.AssertionError: FlowFile content differs from input at byte 287
> with input having value 10 and FlowFile having value 13
> at
> org.apache.nifi.processors.standard.TestConvertCharacterSet.testExpressionLanguageOutput(TestConvertCharacterSet.java:77)
> testExpressionLanguageInput(org.apache.nifi.processors.standard.TestConvertCharacterSet)
> Time elapsed: 0.015 sec <<< FAILURE!
> java.lang.AssertionError: FlowFile content differs from input at byte 287
> with input having value 10 and FlowFile having value 13
> at
> org.apache.nifi.processors.standard.TestConvertCharacterSet.testExpressionLanguageInput(TestConvertCharacterSet.java:61)
> testSimple(org.apache.nifi.processors.standard.TestConvertCharacterSet) Time
> elapsed: 0.04 sec <<< FAILURE!
> java.lang.AssertionError: FlowFile content differs from input at byte 287
> with input having value 10 and FlowFile having value 13
> at
> org.apache.nifi.processors.standard.TestConvertCharacterSet.testSimple(TestConvertCharacterSet.java:45)
> {quote}
> Additionally, org.apache.nifi.processors.standard.TestUnpackContent also has
> some similar failures...
> {quote}
> TestUnpackContent.testFlowFileStreamV2:150 FlowFile content differs from
> input at byte 20 with input having value 13 and FlowFile having value 10
> TestUnpackContent.testFlowFileStreamV3:127 FlowFile content differs from
> input at byte 20 with input having value 13 and FlowFile having value 10
> TestUnpackContent.testTar:72 FlowFile content differs from input at byte 20
> with input having value 13 and FlowFile having value 10
> TestUnpackContent.testZip:104 FlowFile content differs from input at byte
> 20 with input having value 13 and FlowFile having value 10
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-7976) JSON Schema Inference infers long type when all values fit in integer type
[ https://issues.apache.org/jira/browse/NIFI-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Thomsen updated NIFI-7976: --- Fix Version/s: 1.13.0 > JSON Schema Inference infers long type when all values fit in integer type > -- > > Key: NIFI-7976 > URL: https://issues.apache.org/jira/browse/NIFI-7976 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For CSV and XML Schema Inference engines, integral values are checked to see > if they fit into an integer type, and if so, the engine infers "int" type, > otherwise it infers "long" type. However the JSON inference engine only > checks for "bigint" and everything else is "long". > It should also check to see if the values fit in an integer type and infer > "int" in that case. -- This message was sent by Atlassian Jira (v8.3.4#803005)
