[jira] [Updated] (NIFI-12282) Move Hadoop, HBase, and Solr to Optional Profiles
[ https://issues.apache.org/jira/browse/NIFI-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12282: -- Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Move Hadoop, HBase, and Solr to Optional Profiles > - > > Key: NIFI-12282 > URL: https://issues.apache.org/jira/browse/NIFI-12282 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Extension component that depend on Apache Hadoop, Apache HBase, and Apache > Solr libraries account for over 150 MB of libraries. With Apache Hadoop > distributions and supporting infrastructure varying between vendors, > specialized build profiles already exist for different platforms. > Moving these extension NAR bundles to optional build profiles brings the > convenience binary build under 1 GB, which benefits storage and distribution > across Apache Infrastructure and Docker Hub. > Both Apache Kudu and Apache Parquet components have dependencies on the > nifi-hadoop-libraries-nar, so Kudu components should be moved to an optional > profile and Parquet components should be included in the Hadoop profile. > These profiles should have the same activation options as existing profiles. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12282) Move Hadoop, HBase, and Solr to Optional Profiles
[ https://issues.apache.org/jira/browse/NIFI-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780586#comment-17780586 ] ASF subversion and git services commented on NIFI-12282: Commit 6b265e21207df76b8848d0f548387a2fb9e12233 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6b265e2120 ] NIFI-12282 Moved Hadoop and other NARs to Optional Profiles - Moved Hadoop and Parquet NARs to include-hadoop - Moved HBase NARs to include-hbase - Moved Kudu NAR to include-kudu - Moved Solr NAR to include-solr This closes #7942. Signed-off-by: Pierre Villard > Move Hadoop, HBase, and Solr to Optional Profiles > - > > Key: NIFI-12282 > URL: https://issues.apache.org/jira/browse/NIFI-12282 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.latest > > Time Spent: 0.5h > Remaining Estimate: 0h > > Extension component that depend on Apache Hadoop, Apache HBase, and Apache > Solr libraries account for over 150 MB of libraries. With Apache Hadoop > distributions and supporting infrastructure varying between vendors, > specialized build profiles already exist for different platforms. > Moving these extension NAR bundles to optional build profiles brings the > convenience binary build under 1 GB, which benefits storage and distribution > across Apache Infrastructure and Docker Hub. > Both Apache Kudu and Apache Parquet components have dependencies on the > nifi-hadoop-libraries-nar, so Kudu components should be moved to an optional > profile and Parquet components should be included in the Hadoop profile. > These profiles should have the same activation options as existing profiles. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12282 Move Hadoop and other NARs to Optional Profiles [nifi]
asfgit closed pull request #7942: NIFI-12282 Move Hadoop and other NARs to Optional Profiles URL: https://github.com/apache/nifi/pull/7942 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12274 Evaluate conditional ASF self-hosted run-on for ci-workflow [nifi]
exceptionfactory closed pull request #7933: NIFI-12274 Evaluate conditional ASF self-hosted run-on for ci-workflow URL: https://github.com/apache/nifi/pull/7933 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12288) Improve Number Handling in Utilities
[ https://issues.apache.org/jira/browse/NIFI-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12288: Status: Patch Available (was: Open) > Improve Number Handling in Utilities > > > Key: NIFI-12288 > URL: https://issues.apache.org/jira/browse/NIFI-12288 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Several utilities and components, such as FormatUtils, as well as the Wait > and Notify Processors, include imprecise conversion between long and integer > numbers. These references should be updated to maintain the original typing > and use explicit methods when converting to integers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12288 Improve Long and Integer handling in Utilities [nifi]
exceptionfactory opened a new pull request, #7950: URL: https://github.com/apache/nifi/pull/7950 # Summary [NIFI-12288](https://issues.apache.org/jira/browse/NIFI-12288) Improves handling of Long and Integer numbers in several utility classes, as well as Wait and Notify Processors. Updated references previously had implicit conversions, but changes remove unnecessary boxing and use available Math utility methods for standardized conversion behavior. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12289. - Fix Version/s: 1.24.0 Resolution: Fixed > Upgrade browserify-sign to 4.2.2 for Registry > - > > Key: NIFI-12289 > URL: https://issues.apache.org/jira/browse/NIFI-12289 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry, Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The browserify-sign library, which is a transitive dependency of the webpack > build library for Registry, should be upgraded to 4.2.2 to resolve an > associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12289: Component/s: NiFi Registry Tools and Build > Upgrade browserify-sign to 4.2.2 for Registry > - > > Key: NIFI-12289 > URL: https://issues.apache.org/jira/browse/NIFI-12289 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry, Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The browserify-sign library, which is a transitive dependency of the webpack > build library for Registry, should be upgraded to 4.2.2 to resolve an > associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12289: Priority: Minor (was: Major) > Upgrade browserify-sign to 4.2.2 for Registry > - > > Key: NIFI-12289 > URL: https://issues.apache.org/jira/browse/NIFI-12289 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The browserify-sign library, which is a transitive dependency of the webpack > build library for Registry, should be upgraded to 4.2.2 to resolve an > associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780578#comment-17780578 ] ASF subversion and git services commented on NIFI-12289: Commit 0a0731a5d031cdf4f95bc8217886558d47a4007a in nifi's branch refs/heads/support/nifi-1.x from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0a0731a5d0 ] NIFI-12289 Upgraded browserify-sign from 4.2.1 to 4.2.2 This closes #7949 Signed-off-by: David Handermann (cherry picked from commit a71cc4bee33775eb145b6d493504a0f09122ac8c) > Upgrade browserify-sign to 4.2.2 for Registry > - > > Key: NIFI-12289 > URL: https://issues.apache.org/jira/browse/NIFI-12289 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The browserify-sign library, which is a transitive dependency of the webpack > build library for Registry, should be upgraded to 4.2.2 to resolve an > associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780577#comment-17780577 ] ASF subversion and git services commented on NIFI-12289: Commit a71cc4bee33775eb145b6d493504a0f09122ac8c in nifi's branch refs/heads/main from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a71cc4bee3 ] NIFI-12289 Upgraded browserify-sign from 4.2.1 to 4.2.2 This closes #7949 Signed-off-by: David Handermann > Upgrade browserify-sign to 4.2.2 for Registry > - > > Key: NIFI-12289 > URL: https://issues.apache.org/jira/browse/NIFI-12289 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > > The browserify-sign library, which is a transitive dependency of the webpack > build library for Registry, should be upgraded to 4.2.2 to resolve an > associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12289 Bump browserify-sign from 4.2.1 to 4.2.2 in /nifi-registry/nifi-registry-core/nifi-registry-web-ui/src/main [nifi]
dependabot[bot] commented on PR #7949: URL: https://github.com/apache/nifi/pull/7949#issuecomment-1783667172 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12289 Bump browserify-sign from 4.2.1 to 4.2.2 in /nifi-registry/nifi-registry-core/nifi-registry-web-ui/src/main [nifi]
exceptionfactory closed pull request #7949: NIFI-12289 Bump browserify-sign from 4.2.1 to 4.2.2 in /nifi-registry/nifi-registry-core/nifi-registry-web-ui/src/main URL: https://github.com/apache/nifi/pull/7949 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12289) Upgrade browserify-sign to 4.2.2 for Registry
David Handermann created NIFI-12289: --- Summary: Upgrade browserify-sign to 4.2.2 for Registry Key: NIFI-12289 URL: https://issues.apache.org/jira/browse/NIFI-12289 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0 The browserify-sign library, which is a transitive dependency of the webpack build library for Registry, should be upgraded to 4.2.2 to resolve an associated vulnerability, not applicable to runtime behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12277) Add SSLContextService to Slack processors
[ https://issues.apache.org/jira/browse/NIFI-12277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780576#comment-17780576 ] David Handermann commented on NIFI-12277: - [~mbathori] I merged this change into the main branch for NiFi 2.0.0. This change did not apply directly to the support branch, so if you would like to open a new pull request for backporting the changes, feel free to do so. > Add SSLContextService to Slack processors > - > > Key: NIFI-12277 > URL: https://issues.apache.org/jira/browse/NIFI-12277 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add support for custom SSL context usage in PutSlack and PostSlack processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12277) Add SSLContextService to Slack processors
[ https://issues.apache.org/jira/browse/NIFI-12277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12277. - Fix Version/s: 2.0.0 Resolution: Fixed > Add SSLContextService to Slack processors > - > > Key: NIFI-12277 > URL: https://issues.apache.org/jira/browse/NIFI-12277 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add support for custom SSL context usage in PutSlack and PostSlack processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12277) Add SSLContextService to Slack processors
[ https://issues.apache.org/jira/browse/NIFI-12277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780575#comment-17780575 ] ASF subversion and git services commented on NIFI-12277: Commit b2c4baf429d8bf360babc69ae0aec5a963520d38 in nifi's branch refs/heads/main from Mark Bathori [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b2c4baf429 ] NIFI-12277 Added SSLContextService to Slack Processors This closes #7936 Signed-off-by: David Handermann > Add SSLContextService to Slack processors > - > > Key: NIFI-12277 > URL: https://issues.apache.org/jira/browse/NIFI-12277 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Add support for custom SSL context usage in PutSlack and PostSlack processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12277: Add SSLContextService to Slack processors [nifi]
exceptionfactory closed pull request #7936: NIFI-12277: Add SSLContextService to Slack processors URL: https://github.com/apache/nifi/pull/7936 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12282 Move Hadoop and other NARs to Optional Profiles [nifi]
exceptionfactory commented on PR #7942: URL: https://github.com/apache/nifi/pull/7942#issuecomment-1783659408 Thanks for flagging the spacing changes @pvillard31. There were a few tab characters in the nifi-assembly pom.xml, I pushed a commit to replace the rest of the tabs with spaces. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12265 Fix StandardPGPPublicKeyService key search issue with subkey starts with 0 [nifi]
nathluu commented on PR #7926: URL: https://github.com/apache/nifi/pull/7926#issuecomment-1783653112 Hi @exceptionfactory, PR was updated. Please help to review it again. Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12282 Move Hadoop and other NARs to Optional Profiles [nifi]
pvillard31 commented on code in PR #7942: URL: https://github.com/apache/nifi/pull/7942#discussion_r1375116677 ## nifi-assembly/pom.xml: ## @@ -1100,7 +1150,7 @@ language governing permissions and limitations under the License. --> - + Review Comment: Expected? ## nifi-assembly/pom.xml: ## @@ -1115,14 +1165,14 @@ language governing permissions and limitations under the License. --> nifi-accumulo-nar 2.0.0-SNAPSHOT nar - - + + org.apache.nifi nifi-accumulo-services-api-nar 2.0.0-SNAPSHOT nar - - + + Review Comment: Expected? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12276) Upgrade OWASP Dependency Check to 8.4.2 and Address Findings
[ https://issues.apache.org/jira/browse/NIFI-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12276: -- Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade OWASP Dependency Check to 8.4.2 and Address Findings > > > Key: NIFI-12276 > URL: https://issues.apache.org/jira/browse/NIFI-12276 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The OWASP Dependency Check Plugin should be upgraded to 8.4.2. False positive > findings should be updated in the suppression configuration and applicable > libraries should be upgraded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12276 Address Recent Dependency Check Findings [nifi]
asfgit closed pull request #7948: NIFI-12276 Address Recent Dependency Check Findings URL: https://github.com/apache/nifi/pull/7948 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12276) Upgrade OWASP Dependency Check to 8.4.2 and Address Findings
[ https://issues.apache.org/jira/browse/NIFI-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780563#comment-17780563 ] ASF subversion and git services commented on NIFI-12276: Commit 0e1ae2bd6fcbcb9ce11c0bfc66f5f0d05952fe45 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0e1ae2bd6f ] NIFI-12276 Addressed Dependency Check Findings - Added dependency-check GitHub workflow - Upgraded Janino Commons Compiler from 3.1.9 to 3.1.10 - Upgraded Azure SDK BOM from 1.2.16 to 1.2.17 - Upgraded GCP SDK BOM from 26.17.0 to 26.25.0 - Upgraded AWS SDK from 1.12.550 to 1.12.573 - Upgraded Hazelcast from 5.3.2 to 5.3.5 - Upgraded Jersey from 2.40 to 2.41 - Upgraded Camel Salesforce from 3.14.5 to 3.14.9 - Unified ZooKeeper versioning on 3.9.1 - Applied Groovy 2.4.21 to Hive 3 and Iceberg components - Applied gRPC version 1.59.0 to Asana components - Applied Jettison 1.5.4 to Atlas and Hive 3 components - Managed JUnit 4 version to 4.13.2 for MockWebServer - Excluded HBase libraries from Hive 3 following Iceberg approach - Excluded Htrace from HBase components - Upgraded OWASP Dependency Check from 8.4.0 to 8.4.2 - Removed non-applicable dependency check suppressions - Added dependency check suppressions for non-applicable findings Signed-off-by: Pierre Villard This closes #7948. > Upgrade OWASP Dependency Check to 8.4.2 and Address Findings > > > Key: NIFI-12276 > URL: https://issues.apache.org/jira/browse/NIFI-12276 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > The OWASP Dependency Check Plugin should be upgraded to 8.4.2. False positive > findings should be updated in the suppression configuration and applicable > libraries should be upgraded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12287) Standardize Source and Javadoc Skipping for NAR Modules
[ https://issues.apache.org/jira/browse/NIFI-12287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12287: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Standardize Source and Javadoc Skipping for NAR Modules > --- > > Key: NIFI-12287 > URL: https://issues.apache.org/jira/browse/NIFI-12287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Critical > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Project NAR bundles contain other JAR libraries and manifest information, and > source module information is limited to Maven configuration. For this reason, > NAR bundles should not publish sources and javadoc JAR modules. Due to > changes in Maven plugin properties, recent project releases have published > sources unnecessarily. > Project Maven configurations should be updated to avoid publishing sources > and javadoc JARs for any module with a packaging type of NAR or WAR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12287) Standardize Source and Javadoc Skipping for NAR Modules
[ https://issues.apache.org/jira/browse/NIFI-12287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780561#comment-17780561 ] ASF subversion and git services commented on NIFI-12287: Commit 2366132e92951a8fc27097c777d3104a1c396f7b in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2366132e92 ] NIFI-12287 Standardized skipping Source and Javadoc for NAR modules - Added nar-packaging and war-packaging profiles to root Maven configuration - Removed individual properties from NAR module configurations Signed-off-by: Pierre Villard This closes #7947. > Standardize Source and Javadoc Skipping for NAR Modules > --- > > Key: NIFI-12287 > URL: https://issues.apache.org/jira/browse/NIFI-12287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Critical > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Project NAR bundles contain other JAR libraries and manifest information, and > source module information is limited to Maven configuration. For this reason, > NAR bundles should not publish sources and javadoc JAR modules. Due to > changes in Maven plugin properties, recent project releases have published > sources unnecessarily. > Project Maven configurations should be updated to avoid publishing sources > and javadoc JARs for any module with a packaging type of NAR or WAR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12287 Standardize skipping Source and Javadoc for NAR modules [nifi]
asfgit closed pull request #7947: NIFI-12287 Standardize skipping Source and Javadoc for NAR modules URL: https://github.com/apache/nifi/pull/7947 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12288) Improve Number Handling in Utilities
David Handermann created NIFI-12288: --- Summary: Improve Number Handling in Utilities Key: NIFI-12288 URL: https://issues.apache.org/jira/browse/NIFI-12288 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Extensions Reporter: David Handermann Assignee: David Handermann Fix For: 1.latest, 2.latest Several utilities and components, such as FormatUtils, as well as the Wait and Notify Processors, include imprecise conversion between long and integer numbers. These references should be updated to maintain the original typing and use explicit methods when converting to integers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump browserify-sign from 4.2.1 to 4.2.2 in /nifi-registry/nifi-registry-core/nifi-registry-web-ui/src/main [nifi]
dependabot[bot] opened a new pull request, #7949: URL: https://github.com/apache/nifi/pull/7949 Bumps [browserify-sign](https://github.com/crypto-browserify/browserify-sign) from 4.2.1 to 4.2.2. Changelog Sourced from https://github.com/browserify/browserify-sign/blob/main/CHANGELOG.md";>browserify-sign's changelog. https://github.com/browserify/browserify-sign/compare/v4.2.1...v4.2.2";>v4.2.2 - 2023-10-25 Fixed [Tests] log when openssl doesn't support cipher https://redirect.github.com/browserify/browserify-sign/issues/37";>[#37](https://github.com/crypto-browserify/browserify-sign/issues/37) Commits Only apps should have lockfiles https://github.com/browserify/browserify-sign/commit/09a89959393b3c89fedd4f7f3bafa4fec44371d7";>09a8995 [eslint] switch to eslint https://github.com/browserify/browserify-sign/commit/83fe46374b819e959d56d2c0b931308f7451a664";>83fe463 [meta] add npmignore and auto-changelog https://github.com/browserify/browserify-sign/commit/44181838e7dcc4d5d0c568f74312ea28f0bcdfd5";>4418183 [meta] fix package.json indentation https://github.com/browserify/browserify-sign/commit/9ac5a5eaaac8a11eb70ec2febd13745c8764ae02";>9ac5a5e [Tests] migrate from travis to github actions https://github.com/browserify/browserify-sign/commit/d845d855def38e2085d5a21e447a48300f99fa60";>d845d85 [Fix] sign: throw on unsupported padding scheme https://github.com/browserify/browserify-sign/commit/8767739a4516289568bcce9fed8a3b7e23478de9";>8767739 [Fix] properly check the upper bound for DSA signatures https://github.com/browserify/browserify-sign/commit/85994cd6348b50f2fd1b73c54e20881416f44a30";>85994cd [Tests] handle openSSL not supporting a scheme https://github.com/browserify/browserify-sign/commit/f5f17c27f9824de40b5ce8ebd8502111203fd6af";>f5f17c2 [Deps] update bn.js, browserify-rsa, elliptic, parse-asn1, readable-stream, safe-buffer https://github.com/browserify/browserify-sign/commit/a67d0eb4ffceabb366b69da69ce9a223e9d5e96b";>a67d0eb [Dev Deps] update nyc, standard, tape https://github.com/browserify/browserify-sign/commit/cc5350b96702fcba930e0662cf763844fd2f59bf";>cc5350b [Tests] always run coverage; downgrade nyc https://github.com/browserify/browserify-sign/commit/75ce1d5c49a6591dd13422016c07f8f9cae13371";>75ce1d5 [meta] add safe-publish-latest https://github.com/browserify/browserify-sign/commit/dcf49ce85a1a66a6fb31689508d916d7894286a9";>dcf49ce [Tests] add npm run posttest https://github.com/browserify/browserify-sign/commit/75dd8fd6ce56eb37b12e30807e5f913867b21733";>75dd8fd [Dev Deps] update tape https://github.com/browserify/browserify-sign/commit/3aec0386dc8dfba8698be756ec770df863867c84";>3aec038 [Tests] skip unsupported schemes https://github.com/browserify/browserify-sign/commit/703c83ea72db2f45714fe749c6f04b05243ca9a8";>703c83e [Tests] node < 6 lacks array includes https://github.com/browserify/browserify-sign/commit/3aa43cfbc1fdde8481bcdd3bff581574159b869a";>3aa43cf [Dev Deps] fix eslint range https://github.com/browserify/browserify-sign/commit/98d4e0d7ff18871b0ca07415f758a610ccf8ebbe";>98d4e0d Commits https://github.com/browserify/browserify-sign/commit/4af5a90bf8acd9e76e5671dc0497f6ba71968a2c";>4af5a90 v4.2.2 https://github.com/browserify/browserify-sign/commit/3aec0386dc8dfba8698be756ec770df863867c84";>3aec038 [Dev Deps] update tape https://github.com/browserify/browserify-sign/commit/85994cd6348b50f2fd1b73c54e20881416f44a30";>85994cd [Fix] properly check the upper bound for DSA signatures https://github.com/browserify/browserify-sign/commit/9ac5a5eaaac8a11eb70ec2febd13745c8764ae02";>9ac5a5e [meta] fix package.json indentation https://github.com/browserify/browserify-sign/commit/dcf49ce85a1a66a6fb31689508d916d7894286a9";>dcf49ce [meta] add safe-publish-latest https://github.com/browserify/browserify-sign/commit/44181838e7dcc4d5d0c568f74312ea28f0bcdfd5";>4418183 [meta] add npmignore and auto-changelog https://github.com/browserify/browserify-sign/commit/8767739a4516289568bcce9fed8a3b7e23478de9";>8767739 [Fix] sign: throw on unsupported padding scheme https://github.com/browserify/browserify-sign/commit/5f6fb1755917851a40249db7d834da4265ed5950";>5f6fb17 [Tests] log when openssl doesn't support cipher https://github.com/browserify/browserify-sign/commit/f5f17c27f9824de40b5ce8ebd8502111203fd6af";>f5f17c2 [Tests] handle openSSL not supporting a scheme https://github.com/browserify/browserify-sign/commit/d845d855def38e2085d5a21e447a48300f99fa60";>d845d85 [Tests] migrate from travis to github actions Additional commits viewable in https://github.com/crypto-browserify/browserify-sign/compare/v4.2.1...v4.2.2";>compare view Maintainer changes This version was pushed to npm by https://www.npmjs.com/~ljharb";>ljharb, a new releaser for browserify-sign since your current version. [![Dependabot compatibil
[jira] [Updated] (NIFI-12283) Add include-swagger-ui Build Profile for Registry
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12283: Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add include-swagger-ui Build Profile for Registry > - > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12283) Re-instate the no-swagger-ui profile
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12283: Component/s: Tools and Build > Re-instate the no-swagger-ui profile > > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12283) Add include-swagger-ui Build Profile for Registry
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12283: Summary: Add include-swagger-ui Build Profile for Registry (was: Re-instate the no-swagger-ui profile) > Add include-swagger-ui Build Profile for Registry > - > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12285) Allow wget location for py4j to be configurable
[ https://issues.apache.org/jira/browse/NIFI-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12285: Component/s: Tools and Build > Allow wget location for py4j to be configurable > --- > > Key: NIFI-12285 > URL: https://issues.apache.org/jira/browse/NIFI-12285 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The nifi-python-framework pom.xml uses the download-maven-plugin to obtain > the py4j package via wget. The URL for this download location should be > configurable rather than hardcoded in order to support builds performed on > isolated networks. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12285 allow the URL for downloading py4j to be specified by a ma… [nifi]
exceptionfactory closed pull request #7946: NIFI-12285 allow the URL for downloading py4j to be specified by a ma… URL: https://github.com/apache/nifi/pull/7946 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12283 add include-swagger-ui profile with activation by default. [nifi]
exceptionfactory closed pull request #7945: NIFI-12283 add include-swagger-ui profile with activation by default. URL: https://github.com/apache/nifi/pull/7945 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12285) Allow wget location for py4j to be configurable
[ https://issues.apache.org/jira/browse/NIFI-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780531#comment-17780531 ] ASF subversion and git services commented on NIFI-12285: Commit 5ecc12f4051191502bf0b9b18b861c0b862dd2d9 in nifi's branch refs/heads/main from Mark Bean [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5ecc12f405 ] NIFI-12285 Added py4j.url build property The py4j.url property allows the URL for downloading py4j to be specified by a Maven command-line option This closes #7946 Signed-off-by: David Handermann > Allow wget location for py4j to be configurable > --- > > Key: NIFI-12285 > URL: https://issues.apache.org/jira/browse/NIFI-12285 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The nifi-python-framework pom.xml uses the download-maven-plugin to obtain > the py4j package via wget. The URL for this download location should be > configurable rather than hardcoded in order to support builds performed on > isolated networks. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12283) Re-instate the no-swagger-ui profile
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780530#comment-17780530 ] ASF subversion and git services commented on NIFI-12283: Commit 94e746dc4701814ede160d7e0f5793a3e1cf76db in nifi's branch refs/heads/main from Mark Bean [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=94e746dc47 ] NIFI-12283 Added include-swagger-ui profile with activation by default Deactivating prevents attempt to download swagger asset from the Internet allowing for offline builds. This closes #7945 Signed-off-by: David Handermann > Re-instate the no-swagger-ui profile > > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12285) Allow wget location for py4j to be configurable
[ https://issues.apache.org/jira/browse/NIFI-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12285. - Fix Version/s: 2.0.0 Resolution: Fixed > Allow wget location for py4j to be configurable > --- > > Key: NIFI-12285 > URL: https://issues.apache.org/jira/browse/NIFI-12285 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The nifi-python-framework pom.xml uses the download-maven-plugin to obtain > the py4j package via wget. The URL for this download location should be > configurable rather than hardcoded in order to support builds performed on > isolated networks. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12286) Remove nifi-example-bundle
[
https://issues.apache.org/jira/browse/NIFI-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780522#comment-17780522
]
ASF subversion and git services commented on NIFI-12286:
Commit c421172ee241e9c1c8222e0b9b31d68eac792fd2 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c421172ee2 ]
NIFI-12286 Removed nifi-example-bundle
Signed-off-by: Pierre Villard
This closes #7944.
> Remove nifi-example-bundle
> --
>
> Key: NIFI-12286
> URL: https://issues.apache.org/jira/browse/NIFI-12286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Examples
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-example-bundle}} includes a WriteResourceToStream Processor and
> basic elements for Processor handling. The {{nifi-maven-archetypes}} module
> provides a Maven structure and template classes for getting started, and
> numerous available components provide better examples, so this module should
> be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12286) Remove nifi-example-bundle
[
https://issues.apache.org/jira/browse/NIFI-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-12286:
--
Fix Version/s: 2.0.0
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove nifi-example-bundle
> --
>
> Key: NIFI-12286
> URL: https://issues.apache.org/jira/browse/NIFI-12286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Examples
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{nifi-example-bundle}} includes a WriteResourceToStream Processor and
> basic elements for Processor handling. The {{nifi-maven-archetypes}} module
> provides a Maven structure and template classes for getting started, and
> numerous available components provide better examples, so this module should
> be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12286 Remove nifi-example-bundle [nifi]
asfgit closed pull request #7944: NIFI-12286 Remove nifi-example-bundle URL: https://github.com/apache/nifi/pull/7944 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12276 Address Recent Dependency Check Findings [nifi]
exceptionfactory opened a new pull request, #7948: URL: https://github.com/apache/nifi/pull/7948 # Summary [NIFI-12276](https://issues.apache.org/jira/browse/NIFI-12276) Upgrades the OWASP Dependency Check Plugin from 8.4.0 to 8.4.2 and addresses a number of vulnerability findings. Changes include introducing a new `dependency-check` GitHub workflow that runs on a daily schedule to evaluate project dependencies against published vulnerabilities. The workflow prints findings at the end of the build step and also produces an HTML report that can be downloaded for review. Addressing current findings for the main project branch resulted in the following incremental dependency changes: - Upgraded Janino Commons Compiler from 3.1.9 to 3.1.10 - Upgraded Azure SDK BOM from 1.2.16 to 1.2.17 - Upgraded GCP SDK BOM from 26.17.0 to 26.25.0 - Upgraded AWS SDK from 1.12.550 to 1.12.573 - Upgraded Hazelcast from 5.3.2 to 5.3.5 - Upgraded Jersey from 2.40 to 2.41 - Upgraded Camel Salesforce from 3.14.5 to 3.14.9 - Unified ZooKeeper versioning on 3.9.1 - Applied Groovy 2.4.21 to Hive 3 and Iceberg components - Applied gRPC version 1.59.0 to Asana components - Applied Jettison 1.5.4 to Atlas and Hive 3 components - Managed JUnit 4 version to 4.13.2 for MockWebServer - Excluded HBase libraries from Hive 3 following Iceberg approach - Excluded Htrace from HBase components Additional changes include removing non-applicable suppression settings and adding new suppression settings for vulnerabilities that do not have a direct impact on project components. At the time of this writing, the dependency check report flags the following dependencies with associated vulnerabilities: ``` guava-19.0.jar (pkg:maven/com.google.guava/guava@19.0, cpe:2.3:a:google:guava:19.0:*:*:*:*:*:*:*) : CVE-2018-10237 hadoop-client-runtime-3.3.6.jar/META-INF/maven/com.google.protobuf/protobuf-java/pom.xml (pkg:maven/com.google.protobuf/protobuf-java@3.7.1, cpe:2.3:a:google:protobuf-java:3.7.1:*:*:*:*:*:*:*, cpe:2.3:a:protobuf:protobuf:3.7.1:*:*:*:*:*:*:*) : CVE-2022-3171, CVE-2022-3509, CVE-2021-22569 hadoop-client-runtime-3.3.6.jar/META-INF/maven/net.minidev/json-smart/pom.xml (pkg:maven/net.minidev/json-smart@1.3.2, cpe:2.3:a:json-smart_project:json-smart:1.3.2:*:*:*:*:*:*:*, cpe:2.3:a:json-smart_project:json-smart-v1:1.3.2:*:*:*:*:*:*:*) : CVE-2021-31684, CVE-2023-1370 hadoop-client-runtime-3.3.6.jar/META-INF/maven/org.apache.avro/avro/pom.xml (pkg:maven/org.apache.avro/avro@1.7.7) : CVE-2023-39410 hadoop-client-runtime-3.3.6.jar/META-INF/maven/org.eclipse.jetty/jetty-io/pom.xml (pkg:maven/org.eclipse.jetty/jetty-io@9.4.51.v20230217, cpe:2.3:a:eclipse:jetty:9.4.51:20230217:*:*:*:*:*:*, cpe:2.3:a:jetty:jetty:9.4.51:20230217:*:*:*:*:*:*) : CVE-2023-44487, CVE-2023-40167, CVE-2023-36479, CVE-2023-41900 hive-exec-3.1.3.jar/META-INF/maven/com.google.guava/guava/pom.xml (pkg:maven/com.google.guava/guava@11.0.2, cpe:2.3:a:google:guava:11.0.2:*:*:*:*:*:*:*) : CVE-2018-10237 hive-exec-3.1.3.jar/META-INF/maven/org.apache.avro/avro/pom.xml (pkg:maven/org.apache.avro/avro@1.8.2) : CVE-2023-39410 json-io-2.5.1.jar (pkg:maven/com.cedarsoftware/json-io@2.5.1) : CVE-2023-34610 kaml-0.20.0.jar (pkg:maven/com.charleskorn.kaml/kaml@0.20.0, cpe:2.3:a:kaml_project:kaml:0.20.0:*:*:*:*:*:*:*) : CVE-2023-28118, CVE-2021-39194 libthrift-0.9.3.jar (pkg:maven/org.apache.thrift/libthrift@0.9.3, cpe:2.3:a:apache:thrift:0.9.3:*:*:*:*:*:*:*) : CVE-2018-1320, CVE-2019-0205, CVE-2020-13949 netty-3.10.6.Final.jar (pkg:maven/io.netty/netty@3.10.6.Final, cpe:2.3:a:netty:netty:3.10.6:*:*:*:*:*:*:*) : CVE-2019-20444, CVE-2019-20445, CVE-2019-16869, CVE-2020-11612, CVE-2021-37136, CVE-2021-37137, CVE-2021-43797, CVE-2021-21295, CVE-2021-21409, CVE-2021-21290 protobuf-java-2.5.0.jar (pkg:maven/com.google.protobuf/protobuf-java@2.5.0, cpe:2.3:a:google:protobuf-java:2.5.0:*:*:*:*:*:*:*, cpe:2.3:a:protobuf:protobuf:2.5.0:*:*:*:*:*:*:*) : CVE-2022-3171, CVE-2022-3509, CVE-2021-22569 ``` As shown in the dependency names, most of the findings relate to shaded dependencies included in Hadoop and Hive 3 libraries. These libraries are already upgraded to the latest available versions. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes
[jira] [Updated] (NIFI-12276) Upgrade OWASP Dependency Check to 8.4.2 and Address Findings
[ https://issues.apache.org/jira/browse/NIFI-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12276: Fix Version/s: 2.latest Status: Patch Available (was: Open) > Upgrade OWASP Dependency Check to 8.4.2 and Address Findings > > > Key: NIFI-12276 > URL: https://issues.apache.org/jira/browse/NIFI-12276 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > The OWASP Dependency Check Plugin should be upgraded to 8.4.2. False positive > findings should be updated in the suppression configuration and applicable > libraries should be upgraded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12287 Standardize skipping Source and Javadoc for NAR modules [nifi]
exceptionfactory opened a new pull request, #7947: URL: https://github.com/apache/nifi/pull/7947 # Summary [NIFI-12287](https://issues.apache.org/jira/browse/NIFI-12287) Standardizes skipping of Sources and Javadoc JAR generation for NAR and WAR modules. Modern versions of the Maven Source Plugin use `maven.source.skip` as the property name for skipping sources. As a result of historical usage of `source.skip` properties in individual NAR files, recent releases published sources JAR files for each NAR. Changes include adding `nar-packaging` and `war-packaging` profiles to the root Maven configuration, setting `maven.source.skip` and `maven.javadoc.skip` to `true` for the `nar` and `war` packaging types. Centralizing this configuration removes the need for setting these properties in individual NAR configurations. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12287) Standardize Source and Javadoc Skipping for NAR Modules
[ https://issues.apache.org/jira/browse/NIFI-12287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12287: Status: Patch Available (was: Open) > Standardize Source and Javadoc Skipping for NAR Modules > --- > > Key: NIFI-12287 > URL: https://issues.apache.org/jira/browse/NIFI-12287 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Critical > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Project NAR bundles contain other JAR libraries and manifest information, and > source module information is limited to Maven configuration. For this reason, > NAR bundles should not publish sources and javadoc JAR modules. Due to > changes in Maven plugin properties, recent project releases have published > sources unnecessarily. > Project Maven configurations should be updated to avoid publishing sources > and javadoc JARs for any module with a packaging type of NAR or WAR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12287) Standardize Source and Javadoc Skipping for NAR Modules
David Handermann created NIFI-12287: --- Summary: Standardize Source and Javadoc Skipping for NAR Modules Key: NIFI-12287 URL: https://issues.apache.org/jira/browse/NIFI-12287 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0 Project NAR bundles contain other JAR libraries and manifest information, and source module information is limited to Maven configuration. For this reason, NAR bundles should not publish sources and javadoc JAR modules. Due to changes in Maven plugin properties, recent project releases have published sources unnecessarily. Project Maven configurations should be updated to avoid publishing sources and javadoc JARs for any module with a packaging type of NAR or WAR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12240, NIFI-12195: Created new python processors for text embedd… [nifi]
joewitt commented on code in PR #7894: URL: https://github.com/apache/nifi/pull/7894#discussion_r1374928742 ## nifi-python-extensions/nifi-text-embeddings-module/src/main/python/ParseUnstructuredDocument.py: ## @@ -0,0 +1,259 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +import io +import json +from typing import List + +from nifiapi.flowfiletransform import FlowFileTransform, FlowFileTransformResult +from nifiapi.properties import PropertyDescriptor, StandardValidators, PropertyDependency + +PLAIN_TEXT = "Plain Text" +HTML = "HTML" +MARKDOWN = "Markdown" +PDF = "PDF" +EXCEL = "Microsoft Excel" +POWERPOINT = "Microsoft PowerPoint" +WORD = "Microsoft Word" + +PARSING_STRATEGY_AUTO = "Automatic" +PARSING_STRATEGY_HIGH_RES = "High Resolution" +PARSING_STRATEGY_OCR_ONLY = "OCR Only" +PARSING_STRATEGY_FAST = "Fast" + +SINGLE_DOCUMENT = "Single Document" +DOCUMENT_PER_ELEMENT = "Document Per Element" + +TEXT_KEY = "text" +METADATA_KEY = "metadata" + + +class ParseUnstructuredDocument(FlowFileTransform): Review Comment: yeah with a user hat on - i'm parsing a doc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12285 allow the URL for downloading py4j to be specified by a ma… [nifi]
markobean opened a new pull request, #7946:
URL: https://github.com/apache/nifi/pull/7946
…ven command-line option
# Summary
Adds an option to use a maven command-line property to specify the URL used
to downlaod py4j asset during build time. To do so, use
`-Dpy4j.url={some-url-value}`
[NIFI-12285](https://issues.apache.org/jira/browse/NIFI-12285)
# Tracking
Please complete the following tracking steps prior to pull request creation.
### Issue Tracking
- [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue
created
### Pull Request Tracking
- [X] Pull Request title starts with Apache NiFi Jira issue number, such as
`NIFI-0`
- [X] Pull Request commit message starts with Apache NiFi Jira issue number,
as such `NIFI-0`
### Pull Request Formatting
- [X] Pull Request based on current revision of the `main` branch
- [X] Pull Request refers to a feature branch with one commit containing
changes
# Verification
Please indicate the verification steps performed prior to pull request
creation.
### Build
- [X] Build completed using `mvn clean install -P contrib-check`
- [X] JDK 21
### Licensing
- [ ] New dependencies are compatible with the [Apache License
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License
Policy](https://www.apache.org/legal/resolved.html)
- [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE`
files
### Documentation
- [ ] Documentation formatting appears as expected in rendered files
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12240, NIFI-12195: Created new python processors for text embedd… [nifi]
markap14 commented on code in PR #7894: URL: https://github.com/apache/nifi/pull/7894#discussion_r1374906530 ## nifi-python-extensions/nifi-text-embeddings-module/src/main/python/ParseUnstructuredDocument.py: ## @@ -0,0 +1,259 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +import io +import json +from typing import List + +from nifiapi.flowfiletransform import FlowFileTransform, FlowFileTransformResult +from nifiapi.properties import PropertyDescriptor, StandardValidators, PropertyDependency + +PLAIN_TEXT = "Plain Text" +HTML = "HTML" +MARKDOWN = "Markdown" +PDF = "PDF" +EXCEL = "Microsoft Excel" +POWERPOINT = "Microsoft PowerPoint" +WORD = "Microsoft Word" + +PARSING_STRATEGY_AUTO = "Automatic" +PARSING_STRATEGY_HIGH_RES = "High Resolution" +PARSING_STRATEGY_OCR_ONLY = "OCR Only" +PARSING_STRATEGY_FAST = "Fast" + +SINGLE_DOCUMENT = "Single Document" +DOCUMENT_PER_ELEMENT = "Document Per Element" + +TEXT_KEY = "text" +METADATA_KEY = "metadata" + + +class ParseUnstructuredDocument(FlowFileTransform): Review Comment: Thanks @joewitt. I went back and forth on whether to have the word 'unstructured' there or not. The only concern that I had with 'ParseDocument' is that it might be vague. But if you think ParseDocument fits better, will change to that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12240, NIFI-12195: Created new python processors for text embedd… [nifi]
markap14 commented on code in PR #7894: URL: https://github.com/apache/nifi/pull/7894#discussion_r1374905229 ## nifi-python-extensions/nifi-text-embeddings-module/src/main/python/vectorstores/ChromaUtils.py: ## @@ -0,0 +1,155 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +from nifiapi.properties import PropertyDescriptor, StandardValidators, PropertyDependency, ExpressionLanguageScope + +# Connection Strategies +LOCAL_DISK = "Local Disk" +REMOTE_SERVER = "Remote Chroma Server" + +# Authentication Strategies +TOKEN = "Token Authentication" +BASIC_AUTH = "Basic Authentication" +NONE = "None" + +# Transport Protocols +HTTP = "http" +HTTPS = "https" + +CONNECTION_STRATEGY = PropertyDescriptor( +name="Connection Strategy", +description="Specifies how to connect to the Chroma server", +allowable_values=[LOCAL_DISK, REMOTE_SERVER], +default_value=REMOTE_SERVER, +required=True +) +DIRECTORY = PropertyDescriptor( +name="Directory", +description="The Directory that Chroma should use to persist data", +validators=[StandardValidators.NON_EMPTY_VALIDATOR], +required=True, +default_value="./chroma", +dependencies=[PropertyDependency(CONNECTION_STRATEGY, LOCAL_DISK)] +) +HOSTNAME = PropertyDescriptor( +name="Hostname", +description="The hostname to connect to in order to communicate with Chroma", +validators=[StandardValidators.NON_EMPTY_VALIDATOR], +default_value="localhost", +required=True, +dependencies=[PropertyDependency(CONNECTION_STRATEGY, REMOTE_SERVER)] +) +PORT = PropertyDescriptor( +name="Port", +description="The port that the Chroma server is listening on", +validators=[StandardValidators.PORT_VALIDATOR], +default_value="8000", +required=True, +dependencies=[PropertyDependency(CONNECTION_STRATEGY, REMOTE_SERVER)] +) +TRANSPORT_PROTOCOL = PropertyDescriptor( +name="Transport Protocol", +description="Specifies whether connections should be made over http or https", +allowable_values=[HTTP, HTTPS], +default_value=HTTPS, +required=True, +dependencies=[PropertyDependency(CONNECTION_STRATEGY, REMOTE_SERVER)] +) +AUTH_STRATEGY = PropertyDescriptor( +name="Authentication Strategy", +description="Specifies how to authenticate to Chroma server", +allowable_values=[TOKEN, BASIC_AUTH, NONE], +default_value=TOKEN, +required=True, +dependencies=[PropertyDependency(CONNECTION_STRATEGY, REMOTE_SERVER)] +) +AUTH_TOKEN = PropertyDescriptor( +name="Authentication Token", +description="The token to use for authenticating to Chroma server", +validators=[StandardValidators.NON_EMPTY_VALIDATOR], +required=True, +sensitive=True, +dependencies=[PropertyDependency(AUTH_STRATEGY, TOKEN)] +) +USERNAME = PropertyDescriptor( +name="Username", +description="The username to use for authenticating to Chroma server", +validators=[StandardValidators.NON_EMPTY_VALIDATOR], +required=True, +dependencies=[PropertyDependency(AUTH_STRATEGY, BASIC_AUTH)] +) +PASSWORD = PropertyDescriptor( +name="Password", +description="The password to use for authenticating to Chroma server", +validators=[StandardValidators.NON_EMPTY_VALIDATOR], +required=True, +sensitive=True, +dependencies=[PropertyDependency(AUTH_STRATEGY, BASIC_AUTH)] +) +COLLECTION_NAME = PropertyDescriptor( +name="Collection Name", +description="The name of the Chroma Collection to update", Review Comment: Will mention that in the description of the PutChroma Processor. It does not belong here, as this Property Descriptor is used by both PutChroma and QueryChroma. Which means it's a typo to say "the Collection to update" so will address that as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12284) Upgrade Frontend Maven Plugin to 1.14.2
[ https://issues.apache.org/jira/browse/NIFI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780496#comment-17780496 ] ASF subversion and git services commented on NIFI-12284: Commit b1714fe74de887557df1e1926e9e51b1b49b8a7e in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b1714fe74d ] NIFI-12284 Upgraded Frontend Maven Plugin from 1.14.0 to 1.14.2 Signed-off-by: Pierre Villard This closes #7943. > Upgrade Frontend Maven Plugin to 1.14.2 > --- > > Key: NIFI-12284 > URL: https://issues.apache.org/jira/browse/NIFI-12284 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The Frontend Maven Plugin version > [1.14.2|https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142] > includes improvements to avoid corrupted downloads of archives, such as > Node.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12284) Upgrade Frontend Maven Plugin to 1.14.2
[ https://issues.apache.org/jira/browse/NIFI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12284: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Frontend Maven Plugin to 1.14.2 > --- > > Key: NIFI-12284 > URL: https://issues.apache.org/jira/browse/NIFI-12284 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The Frontend Maven Plugin version > [1.14.2|https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142] > includes improvements to avoid corrupted downloads of archives, such as > Node.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12284) Upgrade Frontend Maven Plugin to 1.14.2
[ https://issues.apache.org/jira/browse/NIFI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780495#comment-17780495 ] ASF subversion and git services commented on NIFI-12284: Commit 46b5d8fdc02a8e929b245a39777865b6266e62a7 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=46b5d8fdc0 ] NIFI-12284 Upgraded Frontend Maven Plugin from 1.14.0 to 1.14.2 Signed-off-by: Pierre Villard This closes #7943. > Upgrade Frontend Maven Plugin to 1.14.2 > --- > > Key: NIFI-12284 > URL: https://issues.apache.org/jira/browse/NIFI-12284 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The Frontend Maven Plugin version > [1.14.2|https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142] > includes improvements to avoid corrupted downloads of archives, such as > Node.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12284 Upgrade Frontend Maven Plugin from 1.14.0 to 1.14.2 [nifi]
asfgit closed pull request #7943: NIFI-12284 Upgrade Frontend Maven Plugin from 1.14.0 to 1.14.2 URL: https://github.com/apache/nifi/pull/7943 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12285) Allow wget location for py4j to be configurable
[ https://issues.apache.org/jira/browse/NIFI-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bean reassigned NIFI-12285: Assignee: Mark Bean > Allow wget location for py4j to be configurable > --- > > Key: NIFI-12285 > URL: https://issues.apache.org/jira/browse/NIFI-12285 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > > The nifi-python-framework pom.xml uses the download-maven-plugin to obtain > the py4j package via wget. The URL for this download location should be > configurable rather than hardcoded in order to support builds performed on > isolated networks. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12283) Re-instate the no-swagger-ui profile
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bean updated NIFI-12283: - Status: Patch Available (was: In Progress) > Re-instate the no-swagger-ui profile > > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12283 add include-swagger-ui profile with activation by default. [nifi]
markobean opened a new pull request, #7945: URL: https://github.com/apache/nifi/pull/7945 Deactivating prevents attempt to download swagger asset from the Internet allowing for offline builds. # Summary Re-instating a profile which was removed in a previous commit. Although, this profile is named differently because it is now active by default. Instead of "no-swagger-ui" it is now called "include-swagger-ui". Deactivating the profile (non-default option) is achieved using `-P'!include-swagger-ui'`. Deactivating the profile will prevent the build from attempting to download swagger assets if network connectivity is not available at build time. [NIFI-12283](https://issues.apache.org/jira/browse/NIFI-12283) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12240, NIFI-12195: Created new python processors for text embedd… [nifi]
joewitt commented on code in PR #7894: URL: https://github.com/apache/nifi/pull/7894#discussion_r1374842776 ## nifi-python-extensions/nifi-text-embeddings-module/src/main/python/ParseUnstructuredDocument.py: ## @@ -0,0 +1,259 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +import io +import json +from typing import List + +from nifiapi.flowfiletransform import FlowFileTransform, FlowFileTransformResult +from nifiapi.properties import PropertyDescriptor, StandardValidators, PropertyDependency + +PLAIN_TEXT = "Plain Text" +HTML = "HTML" +MARKDOWN = "Markdown" +PDF = "PDF" +EXCEL = "Microsoft Excel" +POWERPOINT = "Microsoft PowerPoint" +WORD = "Microsoft Word" + +PARSING_STRATEGY_AUTO = "Automatic" +PARSING_STRATEGY_HIGH_RES = "High Resolution" +PARSING_STRATEGY_OCR_ONLY = "OCR Only" +PARSING_STRATEGY_FAST = "Fast" + +SINGLE_DOCUMENT = "Single Document" +DOCUMENT_PER_ELEMENT = "Document Per Element" + +TEXT_KEY = "text" +METADATA_KEY = "metadata" + + +class ParseUnstructuredDocument(FlowFileTransform): Review Comment: would ParseDocument be a better name? It doesn't seem critical to think of it as structured or unstructured and makes the name quite long. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780464#comment-17780464
]
Jonathan Johnson edited comment on NIFI-12232 at 10/27/23 5:00 PM:
---
Hello,
I am also having a number of the "Failed to connect node to cluster..." errors
in my system leaving nodes disconnected from the cluster until stopping NiFi
and allowing the node to recreate its canvas from the cluster. I am trying to
determine if we are experiencing same issues or if this should be its own
ticket.
My logs immediately before the "Failed to connect ..." errors look like:
{code:java}
2023-10-27 09:41:08,373 INFO [Heartbeat Monitor Thread-1]
o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from
NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect
Code=Lack of Heartbeat, Disconnect Reason=Have not received a heartbeat from
node in 3 seconds, updateId=83] to NodeConnectionStatus[nodeId=node1.nifi:9441,
state=CONNECTING, updateId=84]
2023-10-27 09:41:08,452 INFO [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Processing reconnection request from
cluster coordinator.
2023-10-27 09:41:08,720 INFO [Reconnect to Cluster]
o.a.nifi.groups.StandardProcessGroup
Template[id=9cd572fa-2d18-3228-9a10-8f2438ae9459] removed from flow
2023-10-27 09:41:08,722 INFO [Reconnect to Cluster]
o.a.n.f.s.StandardVersionedComponentSynchronizer No differences between current
flow and proposed flow for
StandardProcessGroup[identifier=4e8898ea-018b-1000-14a4-b336fae6590e,name=NiFi
Flow]
2023-10-27 09:41:08,724 INFO [Reconnect to Cluster]
o.a.nifi.groups.StandardProcessGroup
StandardFunnel[id=71590595-018b-1000--94fe7f50-temp-funnel] added to
StandardProcessGroup[identifier=71590595-018b-1000--94fe7f50,name=testetst]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.n.c.s.AffectedComponentSet Starting the following components:
AffectedComponentSet[inputPorts=[], outputPorts=[], remoteInputPorts=[],
remoteOutputPorts=[], processors=[], parameterProviders=[],
flowRegistryCliens=[], controllerServices=[], reportingTasks=[]]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Disconnecting node due to Failed to
properly handle Reconnection request due to
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
to connect node to cluster because local flow controller partially updated.
Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController Will no longer send heartbeats
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController FlowController will stop sending
heartbeats to Cluster Coordinator
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController Cluster State changed from Clustered to
Not Clustered
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.n.c.l.e.CuratorLeaderElectionManager Cannot unregister Leader Election Role
'Primary Node' because that role is not registered
2023-10-27 09:41:08,731 ERROR [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Handling reconnection request failed
due to: org.apache.nifi.controller.serialization.FlowSynchronizationException:
Failed to connect node to cluster because local flow controller partially
updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
to connect node to cluster because local flow controller partially updated.
Administrator should disconnect node and review flow for corruption.
at
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by:
org.apache.nifi.controller.serialization.FlowSynchronizationException:
java.lang.IllegalStateException: Cannot change destination of Connection
because the current destination is running
at
org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: Cannot change destination of
Connection because the current destination is running
at
org.apache.nifi.connectable.StandardConnection.setDestination(StandardConnection.java:310)
at
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateConnectionDestinations(StandardVersionedComponentSynchronizer.java:700)
at
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:405)
... 10 common frames omitted
2023-10-27 09:4
[jira] [Commented] (NIFI-12232) Frequent "failed to connect node to cluster because local flow controller partially updated. Administrator should disconnect node and review flow for corruption"
[
https://issues.apache.org/jira/browse/NIFI-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780464#comment-17780464
]
Jonathan Johnson commented on NIFI-12232:
-
Hello,
I am also having a number of the "Failed to connect node to cluster..." errors
in my system leaving nodes disconnected from the cluster until stopping NiFi
and allowing the node to recreate its canvas from the cluster. I am trying to
determine if we are experiencing same issues or if this should be its own
ticket.
My logs immediately before the "Failed to connect ..." errors look like:
{code:java}
2023-10-27 09:41:08,373 INFO [Heartbeat Monitor Thread-1]
o.a.n.c.c.node.NodeClusterCoordinator Status of node1.nifi:9441 changed from
NodeConnectionStatus[nodeId=node1.nifi:9441, state=DISCONNECTED, Disconnect
Code=Lack of Heartbeat, Disconnect Reason=Have not received a heartbeat from
node in 3 seconds, updateId=83] to NodeConnectionStatus[nodeId=node1.nifi:9441,
state=CONNECTING, updateId=84]
2023-10-27 09:41:08,452 INFO [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Processing reconnection request from
cluster coordinator.
2023-10-27 09:41:08,720 INFO [Reconnect to Cluster]
o.a.nifi.groups.StandardProcessGroup
Template[id=9cd572fa-2d18-3228-9a10-8f2438ae9459] removed from flow
2023-10-27 09:41:08,722 INFO [Reconnect to Cluster]
o.a.n.f.s.StandardVersionedComponentSynchronizer No differences between current
flow and proposed flow for
StandardProcessGroup[identifier=4e8898ea-018b-1000-14a4-b336fae6590e,name=NiFi
Flow]
2023-10-27 09:41:08,724 INFO [Reconnect to Cluster]
o.a.nifi.groups.StandardProcessGroup
StandardFunnel[id=71590595-018b-1000--94fe7f50-temp-funnel] added to
StandardProcessGroup[identifier=71590595-018b-1000--94fe7f50,name=testetst]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.n.c.s.AffectedComponentSet Starting the following components:
AffectedComponentSet[inputPorts=[], outputPorts=[], remoteInputPorts=[],
remoteOutputPorts=[], processors=[], parameterProviders=[],
flowRegistryCliens=[], controllerServices=[], reportingTasks=[]]
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Disconnecting node due to Failed to
properly handle Reconnection request due to
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
to connect node to cluster because local flow controller partially updated.
Administrator should disconnect node and review flow for corruption.
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController Will no longer send heartbeats
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController FlowController will stop sending
heartbeats to Cluster Coordinator
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.apache.nifi.controller.FlowController Cluster State changed from Clustered to
Not Clustered
2023-10-27 09:41:08,731 INFO [Reconnect to Cluster]
o.a.n.c.l.e.CuratorLeaderElectionManager Cannot unregister Leader Election Role
'Primary Node' because that role is not registered
2023-10-27 09:41:08,731 ERROR [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Handling reconnection request failed
due to: org.apache.nifi.controller.serialization.FlowSynchronizationException:
Failed to connect node to cluster because local flow controller partially
updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
to connect node to cluster because local flow controller partially updated.
Administrator should disconnect node and review flow for corruption.
at
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by:
org.apache.nifi.controller.serialization.FlowSynchronizationException:
java.lang.IllegalStateException: Cannot change destination of Connection
because the current destination is running
at
org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:448)
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: Cannot change destination of
Connection because the current destination is running
at
org.apache.nifi.connectable.StandardConnection.setDestination(StandardConnection.java:310)
at
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateConnectionDestinations(StandardVersionedComponentSynchronizer.java:700)
at
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:405)
... 10 common frames omitted
2023-10-27 09:41:08,732 INFO [Reconnect to Cluster]
o.a.n.c.c.nod
Re: [PR] NIFI-11463 Allow IdentifyMimeType to use custom MIME types in addition to defaults [nifi]
NissimShiman commented on PR #7781: URL: https://github.com/apache/nifi/pull/7781#issuecomment-1783230528 Rebased and resolved the minor points. Regarding `migrateProperties(PropertyConfiguration config)`, I looked more into this and currently the behaviour of `PropertyConfiguration`'s [hasProperty()](https://github.com/apache/nifi/blob/main/nifi-api/src/main/java/org/apache/nifi/migration/PropertyConfiguration.java#L79) is to return true on any property found in 2.x (and any property found in 1.x that is not in 2.x that was brought over in a migration) So it always returns true when checking if `CONFIG_STRATEGY` is new (so the potential code in the previous comment won't work for us here). (That being said, it can have its uses when a property from 1.x is no longer found in 2.x. If it returns true then we can call `config.removeProperty()`, so that is perhaps an alternate way for dealing with deprecated properties, but this is not applicable here.) So it doesn't seem `migrateProperties()` has a solution for the use case of this ticket/PR. (or at least not yet) I'm not sure of the way forward here. Maybe this could this just be noted in migration guidance (i.e. that `CONFIG_STRATEGY` will be `PRESET` after migration)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12277: Add SSLContextService to Slack processors [nifi]
mark-bathori commented on PR #7936: URL: https://github.com/apache/nifi/pull/7936#issuecomment-1783170697 Agree on removing the tests, pushed the changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12249 FetchFTP and FetchSFTP processors now write failure reason to 'failure' attribute [nifi]
exceptionfactory commented on code in PR #7929:
URL: https://github.com/apache/nifi/pull/7929#discussion_r1374767594
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFileTransfer.java:
##
@@ -296,6 +298,18 @@ public void onTrigger(final ProcessContext context, final
ProcessSession session
} else {
attributes.put(CoreAttributes.FILENAME.key(), filename);
}
+
+if (failureRelationship != null) {
+attributes.put(FAILURE_REASON_ATTRIBUTE,
failureRelationship.getName());
+flowFile = session.putAllAttributes(flowFile, attributes);
+session.transfer(session.penalize(flowFile),
failureRelationship);
+if (provenanceEventOnFailure) {
+session.getProvenanceReporter().route(flowFile,
failureRelationship);
+}
+cleanupTransfer(transfer, closeConnOnFailure, transferQueue,
host, port);
+return;
+}
Review Comment:
Thanks, that makes sense, and sounds good.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12249 FetchFTP and FetchSFTP processors now write failure reason to 'failure' attribute [nifi]
exceptionfactory commented on code in PR #7929: URL: https://github.com/apache/nifi/pull/7929#discussion_r1374765978 ## nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFileTransfer.java: ## @@ -254,36 +254,38 @@ public void onTrigger(final ProcessContext context, final ProcessSession session transfer = transferWrapper.getFileTransfer(); } +Relationship failureRelationship = null; +boolean closeConnOnFailure = false; +boolean provenanceEventOnFailure = false; Review Comment: Reviewing the changes, it looks like this conditional check can be removed. Although the previous failure handling block did not call the Provenance Reporter on communications failure, this should be changed to always call `getProvenanceReporter().route()` for failures. ```suggestion ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12249 FetchFTP and FetchSFTP processors now write failure reason to 'failure' attribute [nifi]
exceptionfactory commented on code in PR #7929: URL: https://github.com/apache/nifi/pull/7929#discussion_r1374765978 ## nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFileTransfer.java: ## @@ -254,36 +254,38 @@ public void onTrigger(final ProcessContext context, final ProcessSession session transfer = transferWrapper.getFileTransfer(); } +Relationship failureRelationship = null; +boolean closeConnOnFailure = false; +boolean provenanceEventOnFailure = false; Review Comment: Reviewing the changes, it looks like this conditional check can be removed. Although the previous failure handling block did not call the Provenance Reporter on communications failure, this should be changed to always call `getProvenanceReporter().route()` for failures. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12249 FetchFTP and FetchSFTP processors now write failure reason to 'failure' attribute [nifi]
annanys23 commented on code in PR #7929:
URL: https://github.com/apache/nifi/pull/7929#discussion_r1374757819
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFileTransfer.java:
##
@@ -296,6 +298,18 @@ public void onTrigger(final ProcessContext context, final
ProcessSession session
} else {
attributes.put(CoreAttributes.FILENAME.key(), filename);
}
+
+if (failureRelationship != null) {
+attributes.put(FAILURE_REASON_ATTRIBUTE,
failureRelationship.getName());
+flowFile = session.putAllAttributes(flowFile, attributes);
+session.transfer(session.penalize(flowFile),
failureRelationship);
+if (provenanceEventOnFailure) {
+session.getProvenanceReporter().route(flowFile,
failureRelationship);
+}
+cleanupTransfer(transfer, closeConnOnFailure, transferQueue,
host, port);
+return;
+}
Review Comment:
Yes, this was intentional. I would think the other attributes are needed
for a follow on processor to have context (ex: generate email notifications
with similar content to what is being logged in the catch blocks). Also, this
was meant to remove some redundant code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (NIFI-12286) Remove nifi-example-bundle
[
https://issues.apache.org/jira/browse/NIFI-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12286:
Status: Patch Available (was: Open)
> Remove nifi-example-bundle
> --
>
> Key: NIFI-12286
> URL: https://issues.apache.org/jira/browse/NIFI-12286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Examples
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-example-bundle}} includes a WriteResourceToStream Processor and
> basic elements for Processor handling. The {{nifi-maven-archetypes}} module
> provides a Maven structure and template classes for getting started, and
> numerous available components provide better examples, so this module should
> be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12286) Remove nifi-example-bundle
[
https://issues.apache.org/jira/browse/NIFI-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12286:
Priority: Minor (was: Major)
> Remove nifi-example-bundle
> --
>
> Key: NIFI-12286
> URL: https://issues.apache.org/jira/browse/NIFI-12286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Examples
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-example-bundle}} includes a WriteResourceToStream Processor and
> basic elements for Processor handling. The {{nifi-maven-archetypes}} module
> provides a Maven structure and template classes for getting started, and
> numerous available components provide better examples, so this module should
> be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12286 Remove nifi-example-bundle [nifi]
exceptionfactory opened a new pull request, #7944: URL: https://github.com/apache/nifi/pull/7944 # Summary [NIFI-12286](https://issues.apache.org/jira/browse/NIFI-12286) Removes the `nifi-example-bundle` module from `nifi-external`. The `nifi-maven-archetypes` modules contain a better starting point for new modules and numerous existing components also provide examples. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12249 FetchFTP and FetchSFTP processors now write failure reason to 'failure' attribute [nifi]
exceptionfactory commented on code in PR #7929:
URL: https://github.com/apache/nifi/pull/7929#discussion_r1374684426
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFTP.java:
##
@@ -47,7 +47,8 @@
@WritesAttribute(attribute = "ftp.remote.port", description = "The port
that was used to communicate with the remote FTP server"),
@WritesAttribute(attribute = "ftp.remote.filename", description = "The
name of the remote file that was pulled"),
@WritesAttribute(attribute = "filename", description = "The filename is
updated to point to the filename fo the remote file"),
-@WritesAttribute(attribute = "path", description = "If the Remote File
contains a directory name, that directory name will be added to the FlowFile
using the 'path' attribute")
+@WritesAttribute(attribute = "path", description = "If the Remote File
contains a directory name, that directory name will be added to the FlowFile
using the 'path' attribute"),
+@WritesAttribute(attribute = "failure", description = "If the transfer
failed, the failure reason is written to this attribute")
Review Comment:
This should be changed to reflect the updated attribute name:
```suggestion
@WritesAttribute(attribute = "fetch.failure.reason", description = "The
name of the failure relationship applied when routing to any failure
relationship")
```
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchFileTransfer.java:
##
@@ -296,6 +298,18 @@ public void onTrigger(final ProcessContext context, final
ProcessSession session
} else {
attributes.put(CoreAttributes.FILENAME.key(), filename);
}
+
+if (failureRelationship != null) {
+attributes.put(FAILURE_REASON_ATTRIBUTE,
failureRelationship.getName());
+flowFile = session.putAllAttributes(flowFile, attributes);
+session.transfer(session.penalize(flowFile),
failureRelationship);
+if (provenanceEventOnFailure) {
+session.getProvenanceReporter().route(flowFile,
failureRelationship);
+}
+cleanupTransfer(transfer, closeConnOnFailure, transferQueue,
host, port);
+return;
+}
Review Comment:
Moving this logic to a separate block outside of the catch blocks introduces
some potential logic changes, such as the addition of other attributes to the
FlowFile, is that intentional? Otherwise it would be less of an impact to apply
the attribute value in the appropriate catch blocks.
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FetchSFTP.java:
##
@@ -47,7 +47,8 @@
@WritesAttribute(attribute = "sftp.remote.port", description = "The port
that was used to communicate with the remote SFTP server"),
@WritesAttribute(attribute = "sftp.remote.filename", description = "The
name of the remote file that was pulled"),
@WritesAttribute(attribute = "filename", description = "The filename is
updated to point to the filename fo the remote file"),
-@WritesAttribute(attribute = "path", description = "If the Remote File
contains a directory name, that directory name will be added to the FlowFile
using the 'path' attribute")
+@WritesAttribute(attribute = "path", description = "If the Remote File
contains a directory name, that directory name will be added to the FlowFile
using the 'path' attribute"),
+@WritesAttribute(attribute = "failure", description = "If the transfer
failed, the failure reason is written to this attribute")
Review Comment:
This should be changed to reflect the updated attribute name:
```suggestion
@WritesAttribute(attribute = "fetch.failure.reason", description = "The
name of the failure relationship applied when routing to any failure
relationship")
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[PR] MINIFICPP-2260 Fix OpenCV extension build failure on macOS [nifi-minifi-cpp]
martinzink opened a new pull request, #1694: URL: https://github.com/apache/nifi-minifi-cpp/pull/1694 Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12286) Remove nifi-example-bundle
David Handermann created NIFI-12286:
---
Summary: Remove nifi-example-bundle
Key: NIFI-12286
URL: https://issues.apache.org/jira/browse/NIFI-12286
Project: Apache NiFi
Issue Type: Improvement
Components: Examples
Reporter: David Handermann
Assignee: David Handermann
Fix For: 2.latest
The {{nifi-example-bundle}} includes a WriteResourceToStream Processor and
basic elements for Processor handling. The {{nifi-maven-archetypes}} module
provides a Maven structure and template classes for getting started, and
numerous available components provide better examples, so this module should be
removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12273) Incorrect references to command.arguments in ExecuteStreamCommand documentation
[
https://issues.apache.org/jira/browse/NIFI-12273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12273:
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Incorrect references to command.arguments in ExecuteStreamCommand
> documentation
> ---
>
> Key: NIFI-12273
> URL: https://issues.apache.org/jira/browse/NIFI-12273
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website
>Reporter: Andrew M. Lim
>Assignee: Matt Burgess
>Priority: Minor
> Labels: easy-fix, newbie
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Additional Details page for this processor
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html)
> there are references to:
> {{command.arguments}}
> which is incorrect. The references should be:
> {{command.argument}}
> which is what is shown on the main page
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12273) Incorrect references to command.arguments in ExecuteStreamCommand documentation
[
https://issues.apache.org/jira/browse/NIFI-12273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780385#comment-17780385
]
ASF subversion and git services commented on NIFI-12273:
Commit b9a2371afe3e694acfff9ac07b0a2c563e92ebd7 in nifi's branch
refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b9a2371afe ]
NIFI-12273 Fixed command.argument references in ExecuteStreamCommand docs
This closes #7941
Signed-off-by: David Handermann
(cherry picked from commit 880770f992c9bf85629d90031024c3a60356ba2f)
> Incorrect references to command.arguments in ExecuteStreamCommand
> documentation
> ---
>
> Key: NIFI-12273
> URL: https://issues.apache.org/jira/browse/NIFI-12273
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website
>Reporter: Andrew M. Lim
>Assignee: Matt Burgess
>Priority: Minor
> Labels: easy-fix, newbie
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Additional Details page for this processor
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html)
> there are references to:
> {{command.arguments}}
> which is incorrect. The references should be:
> {{command.argument}}
> which is what is shown on the main page
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11677) DeleteHDFS runs tasks with empty incoming connection
[
https://issues.apache.org/jira/browse/NIFI-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-11677:
Fix Version/s: 2.0.0
1.24.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> DeleteHDFS runs tasks with empty incoming connection
>
>
> Key: NIFI-11677
> URL: https://issues.apache.org/jira/browse/NIFI-11677
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.18.0, 1.19.1
> Environment: 64bit redhat linux, java 1.8.0_352, 3 node cluster
>Reporter: Isha Lamboo
>Assignee: Pierre Villard
>Priority: Minor
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The DeleteHDFS processor can operate either with or without an incoming
> connection. When operating *with* an incoming connection that has no
> flowfiles, it still registers as executing tasks and taking a small amount of
> time (in the range of 50-100 millis on our clusters). In our case this
> results in ~200 processors each running 800-1000 tasks per 5 minutes on a 3
> node cluster with 16 CPUs per node.
> This is in contrast to the PutHDFS with an incoming connection which shows as
> 0 tasks/0 millis.
> Reproduce the situation by connecting a (stopped) ListHDFS processor to a
> DeleteHDFS processor with a variable for the path. Start the DeleteHDFS and
> refresh for statistics update.
> Having compared the code for PutHDFS and DeleteHDFS I think I see the cause:
> PutHDFS has this in its OnTrigger method:
> {code:java}
> final FlowFile flowFile = session.get();
> if (flowFile == null) {
> return;
> } {code}
> DeleteHDFS has this in the OnTrigger method:
> {code:java}
> final FlowFile originalFlowFile = session.get();
> // If this processor has an incoming connection, then do not run
> unless a
> // FlowFile is actually sent through
> if (originalFlowFile == null && context.hasIncomingConnection()) {
> context.yield();
> return;
> } {code}
> I'm guessing that the extra context.yield() causes the framework to execute
> some administration tasks and update counters, where it does not for PutHDFS.
> I don't know how much overhead this causes, probably very little, but I'm
> trying to improve performance on a cluster with thread starvation issues and
> high CPU usage and these keep popping up in the summaries looking bad when I
> think they shouldn't.
> The likely solution is to only perform the context.yield() when
> hasIncomingConnection() returns false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11677) DeleteHDFS runs tasks with empty incoming connection
[
https://issues.apache.org/jira/browse/NIFI-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780384#comment-17780384
]
ASF subversion and git services commented on NIFI-11677:
Commit b822c27fb5bf409cd47157da40cd02588bdfcd53 in nifi's branch
refs/heads/support/nifi-1.x from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b822c27fb5 ]
NIFI-11677 Removed non required yield in DeleteHDFS
This closes #7937
Signed-off-by: David Handermann
(cherry picked from commit 1d125e9906090eedb66a7f6f8f1176ac67e007bc)
> DeleteHDFS runs tasks with empty incoming connection
>
>
> Key: NIFI-11677
> URL: https://issues.apache.org/jira/browse/NIFI-11677
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.18.0, 1.19.1
> Environment: 64bit redhat linux, java 1.8.0_352, 3 node cluster
>Reporter: Isha Lamboo
>Assignee: Pierre Villard
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The DeleteHDFS processor can operate either with or without an incoming
> connection. When operating *with* an incoming connection that has no
> flowfiles, it still registers as executing tasks and taking a small amount of
> time (in the range of 50-100 millis on our clusters). In our case this
> results in ~200 processors each running 800-1000 tasks per 5 minutes on a 3
> node cluster with 16 CPUs per node.
> This is in contrast to the PutHDFS with an incoming connection which shows as
> 0 tasks/0 millis.
> Reproduce the situation by connecting a (stopped) ListHDFS processor to a
> DeleteHDFS processor with a variable for the path. Start the DeleteHDFS and
> refresh for statistics update.
> Having compared the code for PutHDFS and DeleteHDFS I think I see the cause:
> PutHDFS has this in its OnTrigger method:
> {code:java}
> final FlowFile flowFile = session.get();
> if (flowFile == null) {
> return;
> } {code}
> DeleteHDFS has this in the OnTrigger method:
> {code:java}
> final FlowFile originalFlowFile = session.get();
> // If this processor has an incoming connection, then do not run
> unless a
> // FlowFile is actually sent through
> if (originalFlowFile == null && context.hasIncomingConnection()) {
> context.yield();
> return;
> } {code}
> I'm guessing that the extra context.yield() causes the framework to execute
> some administration tasks and update counters, where it does not for PutHDFS.
> I don't know how much overhead this causes, probably very little, but I'm
> trying to improve performance on a cluster with thread starvation issues and
> high CPU usage and these keep popping up in the summaries looking bad when I
> think they shouldn't.
> The likely solution is to only perform the context.yield() when
> hasIncomingConnection() returns false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-11677 - remove non required yield in DeleteHDFS [nifi]
exceptionfactory closed pull request #7937: NIFI-11677 - remove non required yield in DeleteHDFS URL: https://github.com/apache/nifi/pull/7937 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-11677) DeleteHDFS runs tasks with empty incoming connection
[
https://issues.apache.org/jira/browse/NIFI-11677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780382#comment-17780382
]
ASF subversion and git services commented on NIFI-11677:
Commit 1d125e9906090eedb66a7f6f8f1176ac67e007bc in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1d125e9906 ]
NIFI-11677 Removed non required yield in DeleteHDFS
This closes #7937
Signed-off-by: David Handermann
> DeleteHDFS runs tasks with empty incoming connection
>
>
> Key: NIFI-11677
> URL: https://issues.apache.org/jira/browse/NIFI-11677
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.18.0, 1.19.1
> Environment: 64bit redhat linux, java 1.8.0_352, 3 node cluster
>Reporter: Isha Lamboo
>Assignee: Pierre Villard
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The DeleteHDFS processor can operate either with or without an incoming
> connection. When operating *with* an incoming connection that has no
> flowfiles, it still registers as executing tasks and taking a small amount of
> time (in the range of 50-100 millis on our clusters). In our case this
> results in ~200 processors each running 800-1000 tasks per 5 minutes on a 3
> node cluster with 16 CPUs per node.
> This is in contrast to the PutHDFS with an incoming connection which shows as
> 0 tasks/0 millis.
> Reproduce the situation by connecting a (stopped) ListHDFS processor to a
> DeleteHDFS processor with a variable for the path. Start the DeleteHDFS and
> refresh for statistics update.
> Having compared the code for PutHDFS and DeleteHDFS I think I see the cause:
> PutHDFS has this in its OnTrigger method:
> {code:java}
> final FlowFile flowFile = session.get();
> if (flowFile == null) {
> return;
> } {code}
> DeleteHDFS has this in the OnTrigger method:
> {code:java}
> final FlowFile originalFlowFile = session.get();
> // If this processor has an incoming connection, then do not run
> unless a
> // FlowFile is actually sent through
> if (originalFlowFile == null && context.hasIncomingConnection()) {
> context.yield();
> return;
> } {code}
> I'm guessing that the extra context.yield() causes the framework to execute
> some administration tasks and update counters, where it does not for PutHDFS.
> I don't know how much overhead this causes, probably very little, but I'm
> trying to improve performance on a cluster with thread starvation issues and
> high CPU usage and these keep popping up in the summaries looking bad when I
> think they shouldn't.
> The likely solution is to only perform the context.yield() when
> hasIncomingConnection() returns false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12273) Incorrect references to command.arguments in ExecuteStreamCommand documentation
[
https://issues.apache.org/jira/browse/NIFI-12273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780383#comment-17780383
]
ASF subversion and git services commented on NIFI-12273:
Commit 880770f992c9bf85629d90031024c3a60356ba2f in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=880770f992 ]
NIFI-12273 Fixed command.argument references in ExecuteStreamCommand docs
This closes #7941
Signed-off-by: David Handermann
> Incorrect references to command.arguments in ExecuteStreamCommand
> documentation
> ---
>
> Key: NIFI-12273
> URL: https://issues.apache.org/jira/browse/NIFI-12273
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website
>Reporter: Andrew M. Lim
>Assignee: Matt Burgess
>Priority: Minor
> Labels: easy-fix, newbie
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the Additional Details page for this processor
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html)
> there are references to:
> {{command.arguments}}
> which is incorrect. The references should be:
> {{command.argument}}
> which is what is shown on the main page
> (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12273: Fix references to command.argument dynamic properties in ExecuteStreamCommand documentation [nifi]
exceptionfactory closed pull request #7941: NIFI-12273: Fix references to command.argument dynamic properties in ExecuteStreamCommand documentation URL: https://github.com/apache/nifi/pull/7941 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12285) Allow wget location for py4j to be configurable
Mark Bean created NIFI-12285: Summary: Allow wget location for py4j to be configurable Key: NIFI-12285 URL: https://issues.apache.org/jira/browse/NIFI-12285 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Mark Bean The nifi-python-framework pom.xml uses the download-maven-plugin to obtain the py4j package via wget. The URL for this download location should be configurable rather than hardcoded in order to support builds performed on isolated networks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12284) Upgrade Frontend Maven Plugin to 1.14.2
[ https://issues.apache.org/jira/browse/NIFI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12284: Status: Patch Available (was: Open) > Upgrade Frontend Maven Plugin to 1.14.2 > --- > > Key: NIFI-12284 > URL: https://issues.apache.org/jira/browse/NIFI-12284 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0, 1.24.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The Frontend Maven Plugin version > [1.14.2|https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142] > includes improvements to avoid corrupted downloads of archives, such as > Node.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12284 Upgrade Frontend Maven Plugin from 1.14.0 to 1.14.2 [nifi]
exceptionfactory opened a new pull request, #7943: URL: https://github.com/apache/nifi/pull/7943 # Summary [NIFI-12284](https://issues.apache.org/jira/browse/NIFI-12284) Upgrades the Frontend Maven Plugin from 1.14.0 to [1.14.2](https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142). The upgraded version includes improvements to avoid corrupted file downloads, which impact user interface modules that require Node.js. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12284) Upgrade Frontend Maven Plugin to 1.14.2
David Handermann created NIFI-12284: --- Summary: Upgrade Frontend Maven Plugin to 1.14.2 Key: NIFI-12284 URL: https://issues.apache.org/jira/browse/NIFI-12284 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0, 1.24.0 The Frontend Maven Plugin version [1.14.2|https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md#1142] includes improvements to avoid corrupted downloads of archives, such as Node.js. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINIFICPP-2260) OpenCV extension build failure on macOS
Martin Zink created MINIFICPP-2260:
--
Summary: OpenCV extension build failure on macOS
Key: MINIFICPP-2260
URL: https://issues.apache.org/jira/browse/MINIFICPP-2260
Project: Apache NiFi MiNiFi C++
Issue Type: Bug
Reporter: Martin Zink
Assignee: Martin Zink
When trying to compile the minifi-opencv extension I encountered this (among
other errors)
{code:java}
Undefined symbols for architecture arm64:
"_AVCaptureSessionPresetMedium", referenced from:
CvCaptureCAM::startCaptureDevice(int) in
libopencv_videoio.a(cap_avfoundation_mac.mm.o) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12107) Utilization column in Cluster Table is not sorting properly
[ https://issues.apache.org/jira/browse/NIFI-12107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulette Hines-Cross updated NIFI-12107: Status: Patch Available (was: In Progress) > Utilization column in Cluster Table is not sorting properly > --- > > Key: NIFI-12107 > URL: https://issues.apache.org/jira/browse/NIFI-12107 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.23.2 >Reporter: Paulette Hines-Cross >Assignee: Paulette Hines-Cross >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > On the Cluster view's CONTENT STORAGE tab, the Utilization column sorts the > values alphabetically rather than numerically. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12283) Re-instate the no-swagger-ui profile
[ https://issues.apache.org/jira/browse/NIFI-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bean reassigned NIFI-12283: Assignee: Mark Bean > Re-instate the no-swagger-ui profile > > > Key: NIFI-12283 > URL: https://issues.apache.org/jira/browse/NIFI-12283 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0 > Environment: building NiFi on an isolated or offline network >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > > There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile > suppressed attempting a `wget` operation to get the swagger-ui component > needed to create the OpenAPI (aka Swagger) presentation of the API. This > operation is not possible when developing offline or in an isolated network > not connected to the Internet. > The profile was removed as part of NIFI-11165. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12283) Re-instate the no-swagger-ui profile
Mark Bean created NIFI-12283: Summary: Re-instate the no-swagger-ui profile Key: NIFI-12283 URL: https://issues.apache.org/jira/browse/NIFI-12283 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0 Environment: building NiFi on an isolated or offline network Reporter: Mark Bean There was a profile in the nifi-registry-web-api, no-swagger-ui. This profile suppressed attempting a `wget` operation to get the swagger-ui component needed to create the OpenAPI (aka Swagger) presentation of the API. This operation is not possible when developing offline or in an isolated network not connected to the Internet. The profile was removed as part of NIFI-11165. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12241 Efficient Parquet Splitting [nifi]
takraj commented on PR #7893: URL: https://github.com/apache/nifi/pull/7893#issuecomment-1782683835 @pvillard31 I've been working on further performance improvements in the last couple of days, and created a new variant of this processor, which calculates the offsets of the row group boundaries, and updated the reader to take these offsets and seek onto these positions in the input file. This is achieved with a special configuration option of the Parquet reader, called 'File Range', that selects only row groups that overlap with the specified start and end offset range. Hopefully this brings major improvement. Could you share how did you extract the processing times from NiFi in your benchmarks? Did you simply take the 'Tasks/Time' indicator, or is there something else that I can monitor? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MINIFICPP-2259) ProcessContext::getProperty should operate on raw pointers
Martin Zink created MINIFICPP-2259: -- Summary: ProcessContext::getProperty should operate on raw pointers Key: MINIFICPP-2259 URL: https://issues.apache.org/jira/browse/MINIFICPP-2259 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Martin Zink Assignee: Martin Zink -- This message was sent by Atlassian Jira (v8.20.10#820010)
