Re: [DISCUSS] MiNiFi C++ 0.13.0 release
Ship it! /|~~~ ///| /| ///| /| \==|===/ ~ On Mon, Nov 28, 2022 at 5:48 PM Joe Witt wrote: > That is a pretty loaded set of changes. Lets do it. > > Thanks > > On Mon, Nov 28, 2022 at 9:46 AM Kevin Doran wrote: > > > > +1, seems like a great time for a new release > > > > On Nov 28, 2022 at 05:14:59, Ferenc Gerlits wrote: > > > > > Hi community, > > > > > > I'd like to initiate a discussion about the next release of MiNiFi > C++. The > > > last release was almost six months ago, and there have been many new > > > features, > > > bug fixes and stability improvements committed to the development > branch > > > since then: 80 tickets closed, over 100 commits. > > > > > > I would be happy to take on RM duties for this release. > > > > > > New features since the 0.12.0 release: > > > > > > - New processors: > > > * ListenTCP > > > * PutTCP > > > * PostElasticSearch > > > * CollectKubernetesPodMetrics > > > - Warn on SSL certificates about to expire > > > - Fix cron-based scheduling > > > - Improve metrics reporting and add support for Prometheus > > > - Improve the performance of several processors (ListenHTTP, AWS, > Azure, > > > GCS) > > > - Support swapping out flow files from memory to disk > > > - Support low-memory use cases with FileSystemRepository > > > - Improve the MQTT processors and add support for MQTT v5.0 > > > - Improve communication with C2, eg. add alert capability > > > - Fix support of native packages in Python scripting > > > - Fix Python scripting on Windows > > > - Add SSL support to the ListenSyslog and ListenTCP processors > > > - Fix the 32-bit build on Windows > > > - Support POST/PUT of large files in InvokeHTTP > > > - Plus upgrade libraries, fix issues reported by clang-tidy, fix memory > > > leaks etc > > > > > > The core API is still not mature enough to be able to commit to it, so > > > in line with previous discussions I suggest releasing it as 0.13.0. > > > > > > Do you agree it is time for a new release? Are there any blockers that > we > > > should definitely include in this release? > > > > > > Thanks, > > > Ferenc > > > >
Re: [DISCUSS] MiNiFi C++ 0.13.0 release
That is a pretty loaded set of changes. Lets do it. Thanks On Mon, Nov 28, 2022 at 9:46 AM Kevin Doran wrote: > > +1, seems like a great time for a new release > > On Nov 28, 2022 at 05:14:59, Ferenc Gerlits wrote: > > > Hi community, > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. The > > last release was almost six months ago, and there have been many new > > features, > > bug fixes and stability improvements committed to the development branch > > since then: 80 tickets closed, over 100 commits. > > > > I would be happy to take on RM duties for this release. > > > > New features since the 0.12.0 release: > > > > - New processors: > > * ListenTCP > > * PutTCP > > * PostElasticSearch > > * CollectKubernetesPodMetrics > > - Warn on SSL certificates about to expire > > - Fix cron-based scheduling > > - Improve metrics reporting and add support for Prometheus > > - Improve the performance of several processors (ListenHTTP, AWS, Azure, > > GCS) > > - Support swapping out flow files from memory to disk > > - Support low-memory use cases with FileSystemRepository > > - Improve the MQTT processors and add support for MQTT v5.0 > > - Improve communication with C2, eg. add alert capability > > - Fix support of native packages in Python scripting > > - Fix Python scripting on Windows > > - Add SSL support to the ListenSyslog and ListenTCP processors > > - Fix the 32-bit build on Windows > > - Support POST/PUT of large files in InvokeHTTP > > - Plus upgrade libraries, fix issues reported by clang-tidy, fix memory > > leaks etc > > > > The core API is still not mature enough to be able to commit to it, so > > in line with previous discussions I suggest releasing it as 0.13.0. > > > > Do you agree it is time for a new release? Are there any blockers that we > > should definitely include in this release? > > > > Thanks, > > Ferenc > >
Re: [DISCUSS] MiNiFi C++ 0.13.0 release
+1, seems like a great time for a new release On Nov 28, 2022 at 05:14:59, Ferenc Gerlits wrote: > Hi community, > > I'd like to initiate a discussion about the next release of MiNiFi C++. The > last release was almost six months ago, and there have been many new > features, > bug fixes and stability improvements committed to the development branch > since then: 80 tickets closed, over 100 commits. > > I would be happy to take on RM duties for this release. > > New features since the 0.12.0 release: > > - New processors: > * ListenTCP > * PutTCP > * PostElasticSearch > * CollectKubernetesPodMetrics > - Warn on SSL certificates about to expire > - Fix cron-based scheduling > - Improve metrics reporting and add support for Prometheus > - Improve the performance of several processors (ListenHTTP, AWS, Azure, > GCS) > - Support swapping out flow files from memory to disk > - Support low-memory use cases with FileSystemRepository > - Improve the MQTT processors and add support for MQTT v5.0 > - Improve communication with C2, eg. add alert capability > - Fix support of native packages in Python scripting > - Fix Python scripting on Windows > - Add SSL support to the ListenSyslog and ListenTCP processors > - Fix the 32-bit build on Windows > - Support POST/PUT of large files in InvokeHTTP > - Plus upgrade libraries, fix issues reported by clang-tidy, fix memory > leaks etc > > The core API is still not mature enough to be able to commit to it, so > in line with previous discussions I suggest releasing it as 0.13.0. > > Do you agree it is time for a new release? Are there any blockers that we > should definitely include in this release? > > Thanks, > Ferenc >
[ANNOUNCE] Apache NiFi 1.19.0 release
Hello The Apache NiFi team would like to announce the release of Apache NiFi 1.19.0. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs of data routing, transformation, and system mediation logic. More details on Apache NiFi can be found here: https://nifi.apache.org/ The release artifacts can be downloaded from here: https://nifi.apache.org/download.html Maven artifacts have been made available and mirrored as per normal ASF artifact processes. Issues closed/resolved for this list can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150 Release note highlights can be found here: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.19.0 Thank you The Apache NiFi team
[RESULT][VOTE] Release Apache NiFi 1.19.0
Apache NiFi Community, I am pleased to announce that the 1.19.0 release of Apache NiFi passes with 6 +1 (binding) votes 5 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread: https://lists.apache.org/thread/jpcc95n73vwt1bq2bf96sv0868pbgpph On Mon, Nov 28, 2022 at 8:35 AM Joe Witt wrote: > +1 binding > > On Mon, Nov 28, 2022 at 5:35 AM Peter Turcsanyi > wrote: > >> +1 (binding) >> >> - Verified signatures and hashes. >> - Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin >> 1.8.0_352-b08), Java 11 (Adoptium Temurin 11.0.17+8) and Java 17 >> (Adoptium Temurin 17.0.5+8). >> - Ran NiFi on the java versions above. >> - Ran flows for testing: >> -- new Snowflake processors (NIFI-10370) >> -- new Iceberg processor (NIFI-10442) >> -- MQTT failover (NIFI-10543) >> -- other smaller changes (NIFI-10349, NIFI-10656, NIFI-10317) >> >> Found some issues but these are not blockers. Jiras created: >> - NIFI-10883: SnowflakeComputingConnectionPool fails on Java 17 >> - NIFI-10884: Conflict resolution in PutAzureDataLakeStorage should >> log the target filename >> - NIFI-10885: ConsumeMQTT should stop client threads >> >> Thanks for RMing Joe! >> >> Regards, >> Peter Turcsanyi >> >> On Mon, Nov 28, 2022 at 4:53 AM Mark Bean wrote: >> > >> > +1 (non-binding) >> > >> > Verified checksums and signatures. >> > Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, >> 11.0.17, >> > 17.0.5 >> > Ran several relatively simple flows in non-cluster mode only. No issues >> > observed. >> > >> > I don't believe this is worth holding up the 1.19.0 release, but while >> > everything worked as expected with Java 8 and 11, there were some issues >> > with Java 17 in generating documentation for several of the "scripted" >> > processors, controller services and a reporting task. The following is >> from >> > the nifi-app.log. And, in the UI, the documentation was not >> full/complete >> > for these processors. >> > >> > 2022-11-27 20:50:27,703 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.processors.script.InvokeScriptedProcessor] >> > 2022-11-27 20:50:28,243 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class org.apache.nifi.processors.script.ExecuteScript] >> > 2022-11-27 20:50:28,311 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.record.sink.script.ScriptedRecordSink] >> > 2022-11-27 20:50:28,313 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.record.script.ScriptedRecordSetWriter] >> > 2022-11-27 20:50:28,315 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> org.apache.nifi.lookup.script.ScriptedLookupService] >> > 2022-11-27 20:50:28,323 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.lookup.script.SimpleScriptedLookupService] >> > 2022-11-27 20:50:28,326 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.rules.handlers.script.ScriptedActionHandler] >> > 2022-11-27 20:50:28,327 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class org.apache.nifi.record.script.ScriptedReader] >> > 2022-11-27 20:50:28,328 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.rules.engine.script.ScriptedRulesEngine] >> > 2022-11-27 20:50:28,521 WARN [main] >> > o.apache.nifi.documentation.DocGenerator Documentation generation >> failed: >> > Component Class [class >> > org.apache.nifi.reporting.script.ScriptedReportingTask] >> > >> > On Sun, Nov 27, 2022 at 4:35 PM Nandor Soma Abonyi >> > wrote: >> > >> > > +1 (non-binding) >> > > >> > > I’ve found two minor issues. I believe none of them is a blocker, but >> we >> > > should follow up on them. Marked them with ***. >> > > >> > > Went through the release helper guide on: >> > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) >> > > Java version: 1.8.0_332, vendor: Temurin >> > > Default locale: en_US, platform encoding: UTF-8 >> > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" >> > > >> > > Imported flows from NiFi registry for these issues and verified them: >> > > - NIFI-10760 - Add Api key authentication option to >> > > ElasticSearchClientServiceImpl >> > > - *** A validation has been removed, which prevented using Basic >> and >> > > Api Key properties together. >> > >
Re: [VOTE] Release Apache NiFi 1.19.0 (RC1)
+1 binding On Mon, Nov 28, 2022 at 5:35 AM Peter Turcsanyi wrote: > +1 (binding) > > - Verified signatures and hashes. > - Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin > 1.8.0_352-b08), Java 11 (Adoptium Temurin 11.0.17+8) and Java 17 > (Adoptium Temurin 17.0.5+8). > - Ran NiFi on the java versions above. > - Ran flows for testing: > -- new Snowflake processors (NIFI-10370) > -- new Iceberg processor (NIFI-10442) > -- MQTT failover (NIFI-10543) > -- other smaller changes (NIFI-10349, NIFI-10656, NIFI-10317) > > Found some issues but these are not blockers. Jiras created: > - NIFI-10883: SnowflakeComputingConnectionPool fails on Java 17 > - NIFI-10884: Conflict resolution in PutAzureDataLakeStorage should > log the target filename > - NIFI-10885: ConsumeMQTT should stop client threads > > Thanks for RMing Joe! > > Regards, > Peter Turcsanyi > > On Mon, Nov 28, 2022 at 4:53 AM Mark Bean wrote: > > > > +1 (non-binding) > > > > Verified checksums and signatures. > > Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, > 11.0.17, > > 17.0.5 > > Ran several relatively simple flows in non-cluster mode only. No issues > > observed. > > > > I don't believe this is worth holding up the 1.19.0 release, but while > > everything worked as expected with Java 8 and 11, there were some issues > > with Java 17 in generating documentation for several of the "scripted" > > processors, controller services and a reporting task. The following is > from > > the nifi-app.log. And, in the UI, the documentation was not full/complete > > for these processors. > > > > 2022-11-27 20:50:27,703 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.processors.script.InvokeScriptedProcessor] > > 2022-11-27 20:50:28,243 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class org.apache.nifi.processors.script.ExecuteScript] > > 2022-11-27 20:50:28,311 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.record.sink.script.ScriptedRecordSink] > > 2022-11-27 20:50:28,313 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.record.script.ScriptedRecordSetWriter] > > 2022-11-27 20:50:28,315 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > org.apache.nifi.lookup.script.ScriptedLookupService] > > 2022-11-27 20:50:28,323 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.lookup.script.SimpleScriptedLookupService] > > 2022-11-27 20:50:28,326 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.rules.handlers.script.ScriptedActionHandler] > > 2022-11-27 20:50:28,327 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class org.apache.nifi.record.script.ScriptedReader] > > 2022-11-27 20:50:28,328 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.rules.engine.script.ScriptedRulesEngine] > > 2022-11-27 20:50:28,521 WARN [main] > > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > > Component Class [class > > org.apache.nifi.reporting.script.ScriptedReportingTask] > > > > On Sun, Nov 27, 2022 at 4:35 PM Nandor Soma Abonyi > > wrote: > > > > > +1 (non-binding) > > > > > > I’ve found two minor issues. I believe none of them is a blocker, but > we > > > should follow up on them. Marked them with ***. > > > > > > Went through the release helper guide on: > > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > > > Java version: 1.8.0_332, vendor: Temurin > > > Default locale: en_US, platform encoding: UTF-8 > > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > > > > > Imported flows from NiFi registry for these issues and verified them: > > > - NIFI-10760 - Add Api key authentication option to > > > ElasticSearchClientServiceImpl > > > - *** A validation has been removed, which prevented using Basic > and > > > Api Key properties together. > > > If I set Username/Password and hide them by selecting Api > Key > > > Authorization Scheme, the client will still use those credentials. If > I set > > > Api Key, the client will add both credentials as a request header. > > > Opened NIFI-10880 for further discussion. > > > - NIFI-10668 - Persist proxy password in remote process group > > > - NIFI-10656 - Log ignored event with info instead of warning in > PutADLS > > > - NIFI-10650 - Fix demarcator is appended to the end of the FlowFile's > > > content by
Re: [VOTE] Release Apache NiFi 1.19.0 (RC1)
+1 (binding) - Verified signatures and hashes. - Built NiFi on Ubuntu 20.04 with Java 8 (Adoptium Temurin 1.8.0_352-b08), Java 11 (Adoptium Temurin 11.0.17+8) and Java 17 (Adoptium Temurin 17.0.5+8). - Ran NiFi on the java versions above. - Ran flows for testing: -- new Snowflake processors (NIFI-10370) -- new Iceberg processor (NIFI-10442) -- MQTT failover (NIFI-10543) -- other smaller changes (NIFI-10349, NIFI-10656, NIFI-10317) Found some issues but these are not blockers. Jiras created: - NIFI-10883: SnowflakeComputingConnectionPool fails on Java 17 - NIFI-10884: Conflict resolution in PutAzureDataLakeStorage should log the target filename - NIFI-10885: ConsumeMQTT should stop client threads Thanks for RMing Joe! Regards, Peter Turcsanyi On Mon, Nov 28, 2022 at 4:53 AM Mark Bean wrote: > > +1 (non-binding) > > Verified checksums and signatures. > Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, 11.0.17, > 17.0.5 > Ran several relatively simple flows in non-cluster mode only. No issues > observed. > > I don't believe this is worth holding up the 1.19.0 release, but while > everything worked as expected with Java 8 and 11, there were some issues > with Java 17 in generating documentation for several of the "scripted" > processors, controller services and a reporting task. The following is from > the nifi-app.log. And, in the UI, the documentation was not full/complete > for these processors. > > 2022-11-27 20:50:27,703 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.processors.script.InvokeScriptedProcessor] > 2022-11-27 20:50:28,243 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.processors.script.ExecuteScript] > 2022-11-27 20:50:28,311 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.record.sink.script.ScriptedRecordSink] > 2022-11-27 20:50:28,313 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.record.script.ScriptedRecordSetWriter] > 2022-11-27 20:50:28,315 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.lookup.script.ScriptedLookupService] > 2022-11-27 20:50:28,323 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.lookup.script.SimpleScriptedLookupService] > 2022-11-27 20:50:28,326 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.rules.handlers.script.ScriptedActionHandler] > 2022-11-27 20:50:28,327 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.record.script.ScriptedReader] > 2022-11-27 20:50:28,328 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.rules.engine.script.ScriptedRulesEngine] > 2022-11-27 20:50:28,521 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.reporting.script.ScriptedReportingTask] > > On Sun, Nov 27, 2022 at 4:35 PM Nandor Soma Abonyi > wrote: > > > +1 (non-binding) > > > > I’ve found two minor issues. I believe none of them is a blocker, but we > > should follow up on them. Marked them with ***. > > > > Went through the release helper guide on: > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > > Java version: 1.8.0_332, vendor: Temurin > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > > > Imported flows from NiFi registry for these issues and verified them: > > - NIFI-10760 - Add Api key authentication option to > > ElasticSearchClientServiceImpl > > - *** A validation has been removed, which prevented using Basic and > > Api Key properties together. > > If I set Username/Password and hide them by selecting Api Key > > Authorization Scheme, the client will still use those credentials. If I set > > Api Key, the client will add both credentials as a request header. > > Opened NIFI-10880 for further discussion. > > - NIFI-10668 - Persist proxy password in remote process group > > - NIFI-10656 - Log ignored event with info instead of warning in PutADLS > > - NIFI-10650 - Fix demarcator is appended to the end of the FlowFile's > > content by ConsumeMQTT > > - NIFI-10644 - Add Message Demarcator-style processing in PublishMQTT > > - NIFI-10543 - Support broker failover in MQTT processors > > - NIFI-10491 - PutAzureBlobStorage_v12 should have Conflict Resolution > > Strategy > > - NIFI-10317 - NullPointerException if AMQP header
Re: [VOTE] Release Apache NiFi 1.19.0 (RC1)
+1 (non-binding) - Went through the helper guide, full clean build, verified signatures and hashes - Started NiFi, created a simple flow - NIFI-10701, NIFI-10857: Run minifi and minifi-c2 ITs, which includes the building of the refactored docker images (dockermaven). Image sizes look good - NIFI-10679: Verified the newly implemented "UPDATE/ASSET" C2 command. The asset was downloaded to the agent's asset directory as expected Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /Users/fkis/.sdkman/candidates/maven/current Java version: 1.8.0_252, vendor: AdoptOpenJDK, runtime: /Users/fkis/.sdkman/candidates/java/8.0.252.hs-adpt/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" On Mon, Nov 28, 2022 at 4:53 AM Mark Bean wrote: > +1 (non-binding) > > Verified checksums and signatures. > Performed full build with -Pcontrib-check using OpenJDK 1.8.0_352, 11.0.17, > 17.0.5 > Ran several relatively simple flows in non-cluster mode only. No issues > observed. > > I don't believe this is worth holding up the 1.19.0 release, but while > everything worked as expected with Java 8 and 11, there were some issues > with Java 17 in generating documentation for several of the "scripted" > processors, controller services and a reporting task. The following is from > the nifi-app.log. And, in the UI, the documentation was not full/complete > for these processors. > > 2022-11-27 20:50:27,703 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.processors.script.InvokeScriptedProcessor] > 2022-11-27 20:50:28,243 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.processors.script.ExecuteScript] > 2022-11-27 20:50:28,311 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.record.sink.script.ScriptedRecordSink] > 2022-11-27 20:50:28,313 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.record.script.ScriptedRecordSetWriter] > 2022-11-27 20:50:28,315 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.lookup.script.ScriptedLookupService] > 2022-11-27 20:50:28,323 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.lookup.script.SimpleScriptedLookupService] > 2022-11-27 20:50:28,326 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.rules.handlers.script.ScriptedActionHandler] > 2022-11-27 20:50:28,327 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class org.apache.nifi.record.script.ScriptedReader] > 2022-11-27 20:50:28,328 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.rules.engine.script.ScriptedRulesEngine] > 2022-11-27 20:50:28,521 WARN [main] > o.apache.nifi.documentation.DocGenerator Documentation generation failed: > Component Class [class > org.apache.nifi.reporting.script.ScriptedReportingTask] > > On Sun, Nov 27, 2022 at 4:35 PM Nandor Soma Abonyi > wrote: > > > +1 (non-binding) > > > > I’ve found two minor issues. I believe none of them is a blocker, but we > > should follow up on them. Marked them with ***. > > > > Went through the release helper guide on: > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > > Java version: 1.8.0_332, vendor: Temurin > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > > > Imported flows from NiFi registry for these issues and verified them: > > - NIFI-10760 - Add Api key authentication option to > > ElasticSearchClientServiceImpl > > - *** A validation has been removed, which prevented using Basic and > > Api Key properties together. > > If I set Username/Password and hide them by selecting Api > Key > > Authorization Scheme, the client will still use those credentials. If I > set > > Api Key, the client will add both credentials as a request header. > > Opened NIFI-10880 for further discussion. > > - NIFI-10668 - Persist proxy password in remote process group > > - NIFI-10656 - Log ignored event with info instead of warning in PutADLS > > - NIFI-10650 - Fix demarcator is appended to the end of the FlowFile's > > content by ConsumeMQTT > > - NIFI-10644 - Add Message Demarcator-style processing in PublishMQTT > > - NIFI-10543 - Support broker failover in MQTT processors > > - NIFI-10491 - PutAzureBlobStorage_v12 should have Conflict Resolution > > Strategy > > - NIFI-10317 -
[DISCUSS] MiNiFi C++ 0.13.0 release
Hi community, I'd like to initiate a discussion about the next release of MiNiFi C++. The last release was almost six months ago, and there have been many new features, bug fixes and stability improvements committed to the development branch since then: 80 tickets closed, over 100 commits. I would be happy to take on RM duties for this release. New features since the 0.12.0 release: - New processors: * ListenTCP * PutTCP * PostElasticSearch * CollectKubernetesPodMetrics - Warn on SSL certificates about to expire - Fix cron-based scheduling - Improve metrics reporting and add support for Prometheus - Improve the performance of several processors (ListenHTTP, AWS, Azure, GCS) - Support swapping out flow files from memory to disk - Support low-memory use cases with FileSystemRepository - Improve the MQTT processors and add support for MQTT v5.0 - Improve communication with C2, eg. add alert capability - Fix support of native packages in Python scripting - Fix Python scripting on Windows - Add SSL support to the ListenSyslog and ListenTCP processors - Fix the 32-bit build on Windows - Support POST/PUT of large files in InvokeHTTP - Plus upgrade libraries, fix issues reported by clang-tidy, fix memory leaks etc The core API is still not mature enough to be able to commit to it, so in line with previous discussions I suggest releasing it as 0.13.0. Do you agree it is time for a new release? Are there any blockers that we should definitely include in this release? Thanks, Ferenc
