[jira] [Updated] (NIFI-12434) Upgrade Spring Framework to 6.1.1 and Spring Boot to 3.2.0 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12434: Status: Patch Available (was: In Progress) > Upgrade Spring Framework to 6.1.1 and Spring Boot to 3.2.0 for Registry > --- > > Key: NIFI-12434 > URL: https://issues.apache.org/jira/browse/NIFI-12434 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Following the release of Spring Framework 6.1.0 and Spring Boot 3.2.0, NiFi > Registry should be upgraded to the latest framework versions, along with > transitive dependencies. > This upgrade should cover the same components as the earlier upgrade to > Spring Framework 6.0.13 for Registry, and separate issues will be used to > track upgrading NiFi and remaining application components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12434 Upgrade Registry to Spring Framework 6.1.1 [nifi]
exceptionfactory opened a new pull request, #8087: URL: https://github.com/apache/nifi/pull/8087 # Summary [NIFI-12434](https://issues.apache.org/jira/browse/NIFI-12434) Upgrades NiFi Registry from Spring Framework 6.0.13 to 6.1.1 along with the following related dependencies: - Upgraded Spring Boot from 3.1.5 to 3.2.0 - Upgraded Spring Security from 6.1.5 to 6.2.0 - Upgraded Jetty from 11.0.18 to 12.0.3 - Upgraded Servlet API from 5.0.0 to 6.0.0 Spring Boot 3.2.0 supports Jetty 12, which depends on Servlet API 6. Jetty 12 moved Servlet API packages to new modules, and Spring Boot 3.2.0 defaults to the latest Jakarta EE 10 modules. This upgrade required several minor adjustments to package names for classes referencing Jetty components in Registry. Additional changes include streamlining several Registry integration tests to reduce the need for filtered component scanning related to Data Source configuration. Following on from the upgrade to Spring Framework 6, which included Flyway 9, additional updates include removing integration test configurations for MariaDB 10.0 and 10.2, which Flyway 9 no longer supports. # 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] [Commented] (NIFI-12435) Update QuestDB to 7.3.5
[ https://issues.apache.org/jira/browse/NIFI-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791455#comment-17791455 ] David Handermann commented on NIFI-12435: - QuestDB 7.3.5 changed the status of the SqlCompiler class, so references need to be updated in the nifi-framework module to support upgrading. > Update QuestDB to 7.3.5 > --- > > Key: NIFI-12435 > URL: https://issues.apache.org/jira/browse/NIFI-12435 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update QuestDB to 7.3.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12435 Update QuestDB to 7.3.5 [nifi]
exceptionfactory closed pull request #8083: NIFI-12435 Update QuestDB to 7.3.5 URL: https://github.com/apache/nifi/pull/8083 -- 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-12436) Update datafaker to 2.0.2
[ https://issues.apache.org/jira/browse/NIFI-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12436. - Fix Version/s: 2.0.0 Resolution: Fixed > Update datafaker to 2.0.2 > - > > Key: NIFI-12436 > URL: https://issues.apache.org/jira/browse/NIFI-12436 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update datafaker to 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12431) Update testcontainers to 1.19.3
[ https://issues.apache.org/jira/browse/NIFI-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12431: Priority: Minor (was: Major) > Update testcontainers to 1.19.3 > --- > > Key: NIFI-12431 > URL: https://issues.apache.org/jira/browse/NIFI-12431 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Update testcontainers to 1.19.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12433: Component/s: NiFi Registry > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12431) Update testcontainers to 1.19.3
[ https://issues.apache.org/jira/browse/NIFI-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12431. - Fix Version/s: 1.25.0 2.0.0 Resolution: Fixed > Update testcontainers to 1.19.3 > --- > > Key: NIFI-12431 > URL: https://issues.apache.org/jira/browse/NIFI-12431 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update testcontainers to 1.19.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12436) Update datafaker to 2.0.2
[ https://issues.apache.org/jira/browse/NIFI-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12436: Priority: Minor (was: Major) > Update datafaker to 2.0.2 > - > > Key: NIFI-12436 > URL: https://issues.apache.org/jira/browse/NIFI-12436 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Update datafaker to 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12433. - Fix Version/s: 1.25.0 2.0.0 Resolution: Fixed > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12433: Priority: Minor (was: Major) > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791452#comment-17791452 ] ASF subversion and git services commented on NIFI-12433: Commit 325f599b21bb9fb27597750167b37875a4364937 in nifi's branch refs/heads/support/nifi-1.x from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=325f599b21 ] NIFI-12433 Upgraded mariadb-java-client from 3.2.0 to 3.3.0 This closes #8082 Signed-off-by: David Handermann (cherry picked from commit fcfb777587d0e030a7c08a7669e86b119d0b7ff4) > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12430) Update unboundid-ldapsdk to 6.0.10
[ https://issues.apache.org/jira/browse/NIFI-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791450#comment-17791450 ] ASF subversion and git services commented on NIFI-12430: Commit 42dcea166e648cfd2988a42a437c29fd827b8f9f in nifi's branch refs/heads/support/nifi-1.x from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=42dcea166e ] NIFI-12430 Upgraded unboundid-ldapsdk from 6.0.9 to 6.0.10 This closes #8080 Signed-off-by: David Handermann (cherry picked from commit 6255a98b22a6d24ec79f0a4c4e91d8fdc6913907) > Update unboundid-ldapsdk to 6.0.10 > -- > > Key: NIFI-12430 > URL: https://issues.apache.org/jira/browse/NIFI-12430 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update unboundid-ldapsdk to 6.0.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12436) Update datafaker to 2.0.2
[ https://issues.apache.org/jira/browse/NIFI-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791449#comment-17791449 ] ASF subversion and git services commented on NIFI-12436: Commit 043097478325dc072c886879792f4d92bc173153 in nifi's branch refs/heads/main from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0430974783 ] NIFI-12436 Upgraded datafaker from 2.0.1 to 2.0.2 This closes #8084 Signed-off-by: David Handermann > Update datafaker to 2.0.2 > - > > Key: NIFI-12436 > URL: https://issues.apache.org/jira/browse/NIFI-12436 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update datafaker to 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12430) Update unboundid-ldapsdk to 6.0.10
[ https://issues.apache.org/jira/browse/NIFI-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12430: Fix Version/s: 1.25.0 2.0.0 Status: Patch Available (was: Open) > Update unboundid-ldapsdk to 6.0.10 > -- > > Key: NIFI-12430 > URL: https://issues.apache.org/jira/browse/NIFI-12430 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.24.0, 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update unboundid-ldapsdk to 6.0.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12430) Update unboundid-ldapsdk to 6.0.10
[ https://issues.apache.org/jira/browse/NIFI-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791446#comment-17791446 ] ASF subversion and git services commented on NIFI-12430: Commit 6255a98b22a6d24ec79f0a4c4e91d8fdc6913907 in nifi's branch refs/heads/main from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6255a98b22 ] NIFI-12430 Upgraded unboundid-ldapsdk from 6.0.9 to 6.0.10 This closes #8080 Signed-off-by: David Handermann > Update unboundid-ldapsdk to 6.0.10 > -- > > Key: NIFI-12430 > URL: https://issues.apache.org/jira/browse/NIFI-12430 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update unboundid-ldapsdk to 6.0.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12430) Update unboundid-ldapsdk to 6.0.10
[ https://issues.apache.org/jira/browse/NIFI-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12430: Priority: Minor (was: Major) > Update unboundid-ldapsdk to 6.0.10 > -- > > Key: NIFI-12430 > URL: https://issues.apache.org/jira/browse/NIFI-12430 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update unboundid-ldapsdk to 6.0.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12431) Update testcontainers to 1.19.3
[ https://issues.apache.org/jira/browse/NIFI-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791451#comment-17791451 ] ASF subversion and git services commented on NIFI-12431: Commit 972fc17c76ffcc39cd04222440723174250e11d9 in nifi's branch refs/heads/support/nifi-1.x from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=972fc17c76 ] NIFI-12431 Upgraded testcontainers from 1.19.1 to 1.19.3 This closes #8081 Signed-off-by: David Handermann (cherry picked from commit a36adfd6cf03985a6a3651ca91d2d1ef42229648) > Update testcontainers to 1.19.3 > --- > > Key: NIFI-12431 > URL: https://issues.apache.org/jira/browse/NIFI-12431 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update testcontainers to 1.19.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12431) Update testcontainers to 1.19.3
[ https://issues.apache.org/jira/browse/NIFI-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791447#comment-17791447 ] ASF subversion and git services commented on NIFI-12431: Commit a36adfd6cf03985a6a3651ca91d2d1ef42229648 in nifi's branch refs/heads/main from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a36adfd6cf ] NIFI-12431 Upgraded testcontainers from 1.19.1 to 1.19.3 This closes #8081 Signed-off-by: David Handermann > Update testcontainers to 1.19.3 > --- > > Key: NIFI-12431 > URL: https://issues.apache.org/jira/browse/NIFI-12431 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update testcontainers to 1.19.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12436 Update datafaker to 2.0.2 [nifi]
exceptionfactory closed pull request #8084: NIFI-12436 Update datafaker to 2.0.2 URL: https://github.com/apache/nifi/pull/8084 -- 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-12433 Update mariadb-java-client to 3.3.0 [nifi]
exceptionfactory closed pull request #8082: NIFI-12433 Update mariadb-java-client to 3.3.0 URL: https://github.com/apache/nifi/pull/8082 -- 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-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791448#comment-17791448 ] ASF subversion and git services commented on NIFI-12433: Commit fcfb777587d0e030a7c08a7669e86b119d0b7ff4 in nifi's branch refs/heads/main from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fcfb777587 ] NIFI-12433 Upgraded mariadb-java-client from 3.2.0 to 3.3.0 This closes #8082 Signed-off-by: David Handermann > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12431 Update testcontainers to 1.19.3 [nifi]
exceptionfactory closed pull request #8081: NIFI-12431 Update testcontainers to 1.19.3 URL: https://github.com/apache/nifi/pull/8081 -- 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-12430 Update unboundid-ldapsdk to 6.0.10 [nifi]
exceptionfactory closed pull request #8080: NIFI-12430 Update unboundid-ldapsdk to 6.0.10 URL: https://github.com/apache/nifi/pull/8080 -- 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-12438) Upgrade Logback to 1.3.13
[ https://issues.apache.org/jira/browse/NIFI-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12438. - Resolution: Fixed > Upgrade Logback to 1.3.13 > - > > Key: NIFI-12438 > URL: https://issues.apache.org/jira/browse/NIFI-12438 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Logback [1.3.13]([https://logback.qos.ch/news.html)] includes a minor bug fix > and incorporates several important improvements added in version 1.3.12. > Logback 1.3.12 mitigates CVE-2023-6378, which applies to socket-based Logback > receivers and not to standard project usage of Logback file appenders. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12438) Upgrade Logback to 1.3.13
[ https://issues.apache.org/jira/browse/NIFI-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791439#comment-17791439 ] ASF subversion and git services commented on NIFI-12438: Commit ff0cfaed82dc0f41c8a9efd9f62c4f186c810ccc in nifi's branch refs/heads/support/nifi-1.x from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ff0cfaed82 ] NIFI-12438 Upgraded Logback from 1.3.11 to 1.3.13 This closes #8085 and #8086 Signed-off-by: David Handermann (cherry picked from commit 24ba6d89c7b42bcdabf1d4053d22ff3fede10942) > Upgrade Logback to 1.3.13 > - > > Key: NIFI-12438 > URL: https://issues.apache.org/jira/browse/NIFI-12438 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Logback [1.3.13]([https://logback.qos.ch/news.html)] includes a minor bug fix > and incorporates several important improvements added in version 1.3.12. > Logback 1.3.12 mitigates CVE-2023-6378, which applies to socket-based Logback > receivers and not to standard project usage of Logback file appenders. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12438 Bump ch.qos.logback:logback-classic from 1.3.11 to 1.3.12 [nifi]
dependabot[bot] closed pull request #8086: NIFI-12438 Bump ch.qos.logback:logback-classic from 1.3.11 to 1.3.12 URL: https://github.com/apache/nifi/pull/8086 -- 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-12438 Bump ch.qos.logback:logback-classic from 1.3.11 to 1.3.12 [nifi]
dependabot[bot] commented on PR #8086: URL: https://github.com/apache/nifi/pull/8086#issuecomment-1833092426 Looks like ch.qos.logback:logback-classic is up-to-date now, so this is no longer needed. -- 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-12438) Upgrade Logback to 1.3.13
[ https://issues.apache.org/jira/browse/NIFI-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791437#comment-17791437 ] ASF subversion and git services commented on NIFI-12438: Commit 24ba6d89c7b42bcdabf1d4053d22ff3fede10942 in nifi's branch refs/heads/main from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=24ba6d89c7 ] NIFI-12438 Upgraded Logback from 1.3.11 to 1.3.13 This closes #8085 and #8086 Signed-off-by: David Handermann > Upgrade Logback to 1.3.13 > - > > Key: NIFI-12438 > URL: https://issues.apache.org/jira/browse/NIFI-12438 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Logback [1.3.13]([https://logback.qos.ch/news.html)] includes a minor bug fix > and incorporates several important improvements added in version 1.3.12. > Logback 1.3.12 mitigates CVE-2023-6378, which applies to socket-based Logback > receivers and not to standard project usage of Logback file appenders. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12438 Bump ch.qos.logback:logback-core from 1.3.11 to 1.3.12 [nifi]
dependabot[bot] commented on PR #8085: URL: https://github.com/apache/nifi/pull/8085#issuecomment-1833090976 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-12438 Bump ch.qos.logback:logback-core from 1.3.11 to 1.3.12 [nifi]
exceptionfactory closed pull request #8085: NIFI-12438 Bump ch.qos.logback:logback-core from 1.3.11 to 1.3.12 URL: https://github.com/apache/nifi/pull/8085 -- 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-12438) Upgrade Logback to 1.3.13
David Handermann created NIFI-12438: --- Summary: Upgrade Logback to 1.3.13 Key: NIFI-12438 URL: https://issues.apache.org/jira/browse/NIFI-12438 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: David Handermann Assignee: David Handermann Fix For: 1.25.0, 2.0.0 Logback [1.3.13]([https://logback.qos.ch/news.html)] includes a minor bug fix and incorporates several important improvements added in version 1.3.12. Logback 1.3.12 mitigates CVE-2023-6378, which applies to socket-based Logback receivers and not to standard project usage of Logback file appenders. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12415) Counters
[ https://issues.apache.org/jira/browse/NIFI-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12415: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Counters > > > Key: NIFI-12415 > URL: https://issues.apache.org/jira/browse/NIFI-12415 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add Counters page. > Add Counters menu option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12415) Counters
[ https://issues.apache.org/jira/browse/NIFI-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791364#comment-17791364 ] ASF subversion and git services commented on NIFI-12415: Commit d14686cb3ae16a501187e527bc32c91449674bb6 in nifi's branch refs/heads/main from Rob Fellows [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d14686cb3a ] [NIFI-12415] Counters (#8077) * [NIFI-12415] Counters page * populate counter the table. * support counter reset. * filtering by name and by context * sorting, including initial sort * added basic tests * Formatted with Prettier * review feedback - removing unused things. * align mat-table usage to a common style * disable the Counter menu item if the user doesn't have counterPermissions.canRead This closes #8077 > Counters > > > Key: NIFI-12415 > URL: https://issues.apache.org/jira/browse/NIFI-12415 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Add Counters page. > Add Counters menu option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12415] Counters [nifi]
mcgilman merged PR #8077: URL: https://github.com/apache/nifi/pull/8077 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump ch.qos.logback:logback-classic from 1.3.11 to 1.3.12 [nifi]
dependabot[bot] opened a new pull request, #8086: URL: https://github.com/apache/nifi/pull/8086 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.3.11 to 1.3.12. Commits https://github.com/qos-ch/logback/commit/0df4ec15d45301b5d0a6e2de6466a17944c3a871;>0df4ec1 prepare release 1.3.12 https://github.com/qos-ch/logback/commit/189af5029addc72c91300e3e53466de5a1ca9894;>189af50 ensure JDK 8 compatibility https://github.com/qos-ch/logback/commit/14a71d02102bc5365398ff388cee065eb99ce141;>14a71d0 cater for array size marked with -1 https://github.com/qos-ch/logback/commit/b8eac23a9de9e05fb6d51160b3f46acd91af9731;>b8eac23 prevent DOS attacks using on malicious serialized input https://github.com/qos-ch/logback/commit/d87dd1221eb23732f4400cb60de725765539a274;>d87dd12 further support for Virtual threads, issues 737 https://github.com/qos-ch/logback/commit/034aaee06785b817d41807ea756ce765ed9c8fb3;>034aaee add support for Virtual threads https://github.com/qos-ch/logback/commit/d6294e579848e5c3cd179d495c3c668d5c642f32;>d6294e5 parameterizable invocation gate delay https://github.com/qos-ch/logback/commit/3b91f6d5137814b89a7c9277279ca630292f17c2;>3b91f6d minor refactoring https://github.com/qos-ch/logback/commit/d94ebec6edfdd6e7e3737e9e4c3cd1551e8cdec0;>d94ebec fix guthub issue 715 https://github.com/qos-ch/logback/commit/c76b3030ce618b8c361f39c09779b0a738baf8a6;>c76b303 minor refactoring for better readability Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.3.11...v_1.3.12;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/nifi/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12417) Process Group Configuration
[ https://issues.apache.org/jira/browse/NIFI-12417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12417: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Process Group Configuration > --- > > Key: NIFI-12417 > URL: https://issues.apache.org/jira/browse/NIFI-12417 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Introduce a dialog for configuring a Process Group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12417) Process Group Configuration
[ https://issues.apache.org/jira/browse/NIFI-12417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791355#comment-17791355 ] ASF subversion and git services commented on NIFI-12417: Commit 05575364a317d052e465bee4ad1ff66473172f3a in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=05575364a3 ] NIFI-12417: Process Group Configuration (#8075) * NIFI-12417: - Process Group Configuration. - Removed unnecessary module imports. * NIFI-12417: - Addressing review feedback. This closes #8075 > Process Group Configuration > --- > > Key: NIFI-12417 > URL: https://issues.apache.org/jira/browse/NIFI-12417 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Introduce a dialog for configuring a Process Group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12417: Process Group Configuration [nifi]
rfellows merged PR #8075: URL: https://github.com/apache/nifi/pull/8075 -- 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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791353#comment-17791353 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] Can you also please let me know the current version of NIFI you are running? Thanks! > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump ch.qos.logback:logback-core from 1.3.11 to 1.3.12 [nifi]
dependabot[bot] opened a new pull request, #8085: URL: https://github.com/apache/nifi/pull/8085 Bumps [ch.qos.logback:logback-core](https://github.com/qos-ch/logback) from 1.3.11 to 1.3.12. Commits https://github.com/qos-ch/logback/commit/0df4ec15d45301b5d0a6e2de6466a17944c3a871;>0df4ec1 prepare release 1.3.12 https://github.com/qos-ch/logback/commit/189af5029addc72c91300e3e53466de5a1ca9894;>189af50 ensure JDK 8 compatibility https://github.com/qos-ch/logback/commit/14a71d02102bc5365398ff388cee065eb99ce141;>14a71d0 cater for array size marked with -1 https://github.com/qos-ch/logback/commit/b8eac23a9de9e05fb6d51160b3f46acd91af9731;>b8eac23 prevent DOS attacks using on malicious serialized input https://github.com/qos-ch/logback/commit/d87dd1221eb23732f4400cb60de725765539a274;>d87dd12 further support for Virtual threads, issues 737 https://github.com/qos-ch/logback/commit/034aaee06785b817d41807ea756ce765ed9c8fb3;>034aaee add support for Virtual threads https://github.com/qos-ch/logback/commit/d6294e579848e5c3cd179d495c3c668d5c642f32;>d6294e5 parameterizable invocation gate delay https://github.com/qos-ch/logback/commit/3b91f6d5137814b89a7c9277279ca630292f17c2;>3b91f6d minor refactoring https://github.com/qos-ch/logback/commit/d94ebec6edfdd6e7e3737e9e4c3cd1551e8cdec0;>d94ebec fix guthub issue 715 https://github.com/qos-ch/logback/commit/c76b3030ce618b8c361f39c09779b0a738baf8a6;>c76b303 minor refactoring for better readability Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.3.11...v_1.3.12;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/nifi/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12417: Process Group Configuration [nifi]
mcgilman commented on PR #8075: URL: https://github.com/apache/nifi/pull/8075#issuecomment-1832650893 > Per our offline discussion about moving the Controller Service listing out of the Process Group configuration dialog... I think we can now update the logic in `canvat-utils.service.ts#isConfigurable` to not blindly allow the pg configuration screen to be opened. Not positive and correct me if I'm wrong, but I suspect the original intent here was that we couldn't prevent the user from seeing the controller services of a process group if the user didn't have read access to the PG itself. Now that we plan to have a different dialog for this, we don't need to support a read-only mode for the pg configuration. This is correct. Previously users could have access to Services within the Process Group but not the Process Group itself. By pulling the service listing into its own page we no longer need to _always_ support configuring the Process Group. I'll update the `CanvasUtils` accordingly. This PR does not currently allow the user to configure the current Process Group. I'll update this PR to guard against this case so there are no errors but actually supporting configuring the current Process Group will come in a follow-up effort. I've already begun creating the service listing and introducing a new route for configuring the current Process Group would conflict with those 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
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791288#comment-17791288 ] Philipp Korniets commented on NIFI-11167: - On UNIX system. I will give details tomorrow as am not near computer anymore. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12415] Counters [nifi]
rfellows commented on code in PR #8077:
URL: https://github.com/apache/nifi/pull/8077#discussion_r1409781418
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/counters/ui/counter-listing/counter-table/counter-table.component.ts:
##
@@ -0,0 +1,143 @@
+/*
+ * 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 { AfterViewInit, Component, EventEmitter, Input, OnInit, Output,
ViewChild } from '@angular/core';
+import { CounterEntity } from '../../../state/counter-listing';
+import { MatTableDataSource } from '@angular/material/table';
+import { MatSort } from '@angular/material/sort';
+import { FormBuilder, FormGroup } from '@angular/forms';
+import { debounceTime, filter } from 'rxjs';
+
+@Component({
+selector: 'counter-table',
+templateUrl: './counter-table.component.html',
+styleUrls: ['./counter-table.component.scss',
'../../../../../../assets/styles/listing-table.scss']
+})
+export class CounterTable implements AfterViewInit {
+private _canModifyCounters: boolean = false;
+filterTerm: string = '';
+filterColumn: 'context' | 'name' = 'name';
+totalCount: number = 0;
+filteredCount: number = 0;
+
+displayedColumns: string[] = ['context', 'name', 'value'];
+dataSource: MatTableDataSource = new
MatTableDataSource();
+filterForm: FormGroup;
+
+@Input() initialSortColumn: 'context' | 'name' = 'context';
+@Input() initialSortDirection: 'asc' | 'desc' = 'asc';
+
+@Input() set counters(counterEntities: CounterEntity[]) {
+this.dataSource = new
MatTableDataSource(counterEntities);
+this.dataSource.sort = this.sort;
+this.dataSource.sortingDataAccessor = (data: CounterEntity,
displayColumn: string) => {
+switch (displayColumn) {
+case 'context':
+return this.formatContext(data);
+case 'name':
+return this.formatName(data);
+case 'value':
+return data.valueCount;
+default:
+return '';
+}
+};
+
+this.dataSource.filterPredicate = (data: CounterEntity, filter:
string) => {
+const filterArray = filter.split('|');
+const filterTerm = filterArray[0];
+const filterColumn = filterArray[1];
+
+if (filterColumn === 'name') {
+return
data.name.toLowerCase().indexOf(filterTerm.toLowerCase()) >= 0;
+} else {
+return
data.context.toLowerCase().indexOf(filterTerm.toLowerCase()) >= 0;
+}
+};
+this.totalCount = counterEntities.length;
+this.filteredCount = counterEntities.length;
+
+// apply any filtering to the new data
+const filterTerm = this.filterForm.get('filterTerm')?.value;
+if (filterTerm?.length > 0) {
+const filterColumn = this.filterForm.get('filterColumn')?.value;
+this.applyFilter(filterTerm, filterColumn);
+}
+}
+
+@Input()
+set canModifyCounters(canWrite: boolean) {
+if (canWrite) {
+this.displayedColumns = ['context', 'name', 'value', 'reset'];
+} else {
+this.displayedColumns = ['context', 'name', 'value'];
+}
+this._canModifyCounters = canWrite;
+}
+
+get canModifyCounters(): boolean {
+return this._canModifyCounters;
+}
+
+@Output() resetCounter: EventEmitter = new
EventEmitter();
+@Output() selectCounter: EventEmitter = new
EventEmitter();
Review Comment:
Good catch. No it is not needed.
--
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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791284#comment-17791284 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 7:37 PM: --- [~iiojj2] Are you on Windows? It works on Linux for me without changing. If you are still having an issue please submit a ticket. Thanks! was (Author: JIRAUSER294662): [~iiojj2] Are you on Windows? It works on Linux for me without changing. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791284#comment-17791284 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] Are you on Windows? It works on Linux for me without changing. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791282#comment-17791282 ] Philipp Korniets commented on NIFI-11167: - Why? There is a bug I think in ExcelReader. File comes this way to me from.external provider and ExcelReader can't handle it. I can't change it, sorry. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12417: Process Group Configuration [nifi]
mcgilman commented on code in PR #8075:
URL: https://github.com/apache/nifi/pull/8075#discussion_r1409766288
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/styles.scss:
##
@@ -293,6 +293,15 @@ a:hover {
min-width: 760px;
}
+.full-screen-dialog {
+position: absolute !important;
+top: 25px;
+bottom: 25px;
+right: 25px;
+left: 25px;
+max-width: none !important;
+}
+
Review Comment:
You're correct that is not used right now. I was originally going to put the
service listing with the process group configuration. However, that is being
moved into its own view so this is currently unused. I thought about removing
it but left it in place because I suspected we'd need it for other features in
the future (docs, custom ui, etc). We are also not using all the other types of
dialogs currently.
That said, I'm happy to remove this and we can reintroduce it once it's
needed.
--
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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791279#comment-17791279 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] Try the same change I suggested earlier for cell E20 > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12415] Counters [nifi]
mcgilman commented on code in PR #8077:
URL: https://github.com/apache/nifi/pull/8077#discussion_r1409757105
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/counters/ui/counter-listing/counter-table/counter-table.component.ts:
##
@@ -0,0 +1,143 @@
+/*
+ * 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 { AfterViewInit, Component, EventEmitter, Input, OnInit, Output,
ViewChild } from '@angular/core';
+import { CounterEntity } from '../../../state/counter-listing';
+import { MatTableDataSource } from '@angular/material/table';
+import { MatSort } from '@angular/material/sort';
+import { FormBuilder, FormGroup } from '@angular/forms';
+import { debounceTime, filter } from 'rxjs';
Review Comment:
I think `filter` is unused.
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/counters/ui/counter-listing/counter-table/counter-table.component.ts:
##
@@ -0,0 +1,143 @@
+/*
+ * 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 { AfterViewInit, Component, EventEmitter, Input, OnInit, Output,
ViewChild } from '@angular/core';
Review Comment:
I think `OnInit` is unused.
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/counters/ui/counter-listing/counter-table/counter-table.component.ts:
##
@@ -0,0 +1,143 @@
+/*
+ * 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 { AfterViewInit, Component, EventEmitter, Input, OnInit, Output,
ViewChild } from '@angular/core';
+import { CounterEntity } from '../../../state/counter-listing';
+import { MatTableDataSource } from '@angular/material/table';
+import { MatSort } from '@angular/material/sort';
+import { FormBuilder, FormGroup } from '@angular/forms';
+import { debounceTime, filter } from 'rxjs';
+
+@Component({
+selector: 'counter-table',
+templateUrl: './counter-table.component.html',
+styleUrls: ['./counter-table.component.scss',
'../../../../../../assets/styles/listing-table.scss']
+})
+export class CounterTable implements AfterViewInit {
+private _canModifyCounters: boolean = false;
+filterTerm: string = '';
+filterColumn: 'context' | 'name' = 'name';
+totalCount: number = 0;
+filteredCount: number = 0;
+
+displayedColumns: string[] = ['context', 'name', 'value'];
+dataSource: MatTableDataSource = new
MatTableDataSource();
+filterForm: FormGroup;
+
+@Input() initialSortColumn: 'context' | 'name' = 'context';
+@Input() initialSortDirection: 'asc' | 'desc' = 'asc';
+
+
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791273#comment-17791273 ] Philipp Korniets edited comment on NIFI-11167 at 11/29/23 7:08 PM: --- This a file with formula failure using ExcelReader. Most of the time we can't change files because we receive them from external providers. was (Author: iiojj2): This a file with formula failure using ExcelReader > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1409745610
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttribute.java:
##
@@ -0,0 +1,273 @@
+/*
+ * 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.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
Review Comment:
Well spotted, I adopted your suggested description.
--
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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791273#comment-17791273 ] Philipp Korniets commented on NIFI-11167: - This a file with formula failure using ExcelReader > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1409749624
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttribute.java:
##
@@ -0,0 +1,273 @@
+/*
+ * 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.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
+@UseCase(
+description = "Retain all FlowFile attributes matching a regular
expression",
+configuration = """
+Set "Filter mode" to "Retain".
+Set "Attribute matching strategy" to "Use regular expression".
+Specify the "Regular expression to filter attributes", e.g.
"my-property|a-prefix[.].*".
+"""
+)
+@UseCase(
+description = "Remove only a specified set of FlowFile attributes",
+configuration = """
+Set "Filter mode" to "Remove".
+Set "Attribute matching strategy" to "Enumerate attributes".
+Specify the set of "Set of attributes to filter" using the
delimiter comma ',', e.g. "my-property,other,filename".
+"""
+)
+public class FilterAttribute extends AbstractProcessor {
+
+public static final Relationship REL_SUCCESS = new Relationship.Builder()
+.description("All successful FlowFiles are routed to this
relationship").name("success").build();
+
+private final static Set relationships =
Collections.singleton(REL_SUCCESS);
+
+
+public static final AllowableValue FILTER_MODE_VALUE_RETAIN = new
AllowableValue(
+"RETAIN",
+"Retain",
+"Retains only the attributes matching the filter, all other
attributes are removed."
+);
+
+public static final AllowableValue FILTER_MODE_VALUE_REMOVE = new
AllowableValue(
+"REMOVE",
+"Remove",
+"Removes the attributes matching the filter, all other attributes
are retained."
+);
+
+public static final PropertyDescriptor FILTER_MODE = new
PropertyDescriptor.Builder()
+.name("FILTER_MODE")
+.displayName("Filter mode")
+.description("Specifies the strategy to apply on filtered
attributes. Either 'Remove' or 'Retain' only the matching attributes.")
+.required(true)
+.allowableValues(FILTER_MODE_VALUE_RETAIN,
FILTER_MODE_VALUE_REMOVE)
+
.expressionLanguageSupported(ExpressionLanguageScope.FLOWFILE_ATTRIBUTES)
Review Comment:
These are some good remarks, thank
Re: [PR] NIFI-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1409745610
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttribute.java:
##
@@ -0,0 +1,273 @@
+/*
+ * 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.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
Review Comment:
Well spotted, I adopted your 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-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on PR #8049: URL: https://github.com/apache/nifi/pull/8049#issuecomment-1832523329 I made so small changes to the mentioned parts of the code. I'll explain my thoughts on the changes in the corresponding review conversations. Thank you for the reviews and the kind words @mosermw. -- 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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791262#comment-17791262 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:55 PM: --- [~iiojj2] What do you want me to check for? was (Author: JIRAUSER294662): [~iiojj2] What do you want me to exactly check? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791262#comment-17791262 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] What do you want me to exactly check? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791254#comment-17791254 ] Philipp Korniets commented on NIFI-11167: - [^Test Sheet-formula.xlsx] please check this file > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Korniets updated NIFI-11167: Attachment: Test Sheet-formula.xlsx > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, Test Sheet-formula.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791245#comment-17791245
]
Daniel Stieglitz commented on NIFI-11167:
-
[~iiojj2] If I would have to guess change cell E21
from
{code:java}
=E10+E19{code}
to
{code:java}
=SUM(E10,E19){code}
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791238#comment-17791238
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 6:31 PM:
---
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
For us, keeping names of columns as they are is essential because this is how
we talk to data providers and business owners. When I construct a formula in
QueryRecords I clearly operate with column names from the file which everyone
can see and check themselves in the raw file.
P.S. still working on test file for
{noformat}
java.lang.IllegalStateException: This cell has a shared formula and it seems
setReadSharedFormulas has been set to false or the formula can't be evaluated
{noformat}
was (Author: iiojj2):
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
For us, keeping names of columns as they are is essential because this is how
we talk to data providers and business owners. When I construct a formula in
QueryRecords I clearly operate with column names from the file which every see
and check themselves in the raw file.
P.S. still working on test file for
{noformat}
java.lang.IllegalStateException: This cell has a shared formula and it seems
setReadSharedFormulas has been set to false or the formula can't be evaluated
{noformat}
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791238#comment-17791238
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 6:29 PM:
---
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
For us, keeping names of columns as they are is essential because this is how
we talk to data providers and business owners. When I construct a formula in
QueryRecords I clearly operate with column names from the file which every see
and check themselves in the raw file.
P.S. still working on test file for
{noformat}
java.lang.IllegalStateException: This cell has a shared formula and it seems
setReadSharedFormulas has been set to false or the formula can't be evaluated
{noformat}
was (Author: iiojj2):
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
P.S. still working on test file for
{noformat}
java.lang.IllegalStateException: This cell has a shared formula and it seems
setReadSharedFormulas has been set to false or the formula can't be evaluated
{noformat}
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791238#comment-17791238
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 6:20 PM:
---
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
P.S. still working on test file for
{noformat}
java.lang.IllegalStateException: This cell has a shared formula and it seems
setReadSharedFormulas has been set to false or the formula can't be evaluated
{noformat}
was (Author: iiojj2):
To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner
and understandable for other users.
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791238#comment-17791238 ] Philipp Korniets commented on NIFI-11167: - To tell you the truth, i'd rather keep using ConvertExcelToCSV - much cleaner and understandable for other users. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:15 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader (with infer schema strategy) without skipping the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names (i.e. set 'Include Header Line' to false) and then read it in again with a CSVReader in order to obtain the column names you want which will be on the first line? was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use QueryRecord with Excel reader (with infer schema strategy) without skipping the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader in order to obtain the column names you want which will be on the first line? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:11 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader (with infer schema strategy) without skipping the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader in order to obtain the column names you want which will be on the first line? was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use QueryRecord with Excel reader (with infer schema strategy) without skipping the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader in order to obtain the column names you want? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:10 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader (with infer schema strategy) without skipping the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader in order to obtain the column names you want? was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader? You would then get the column names you wanted. > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:08 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader? was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s), write out the csv with the CSVRecordSetWriter and not write out the column names and then read it in again with a CSVReader? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:09 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader? You would then get the column names you wanted. was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s) with a SQL query, write out the csv with the CSVRecordSetWriter but do not write out the column names and then read it in again with a CSVReader? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) * Counters (NIFI-12415) * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing ** Create ** Configure ** Delete * Configure Processor ** Service Link ** Create inline Service ** Parameter Link ** Convert to Parameter * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary * Counters (NIFI-12415) * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing ** Create ** Configure ** Delete * Configure Processor ** Service Link ** Create inline Service ** Parameter Link ** Convert to Parameter * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > The purpose of this Jira is to track all remaining items following the > initial commit [1] for NIFI-11481. The description will be kept up to date > with remaining features, tasks, and improvements. As each items is worked, a > new sub task Jira will be created and referenced in this description. > * Support Parameters in Properties with Allowable Values (NIFI-12401) > * Summary (NIFI-12437) > * Counters (NIFI-12415) > * Bulletin Board > * Provenance > ** Replay from context menu > * Flow Analysis Rules > * Registry Clients > * Parameter Providers > * Cluster > * Flow Configuration History > * Node Status History > * Users > * Policies > * Help > * About > * Show Upstream/Downstream > * Align > * List Queue > * Empty [all] Queue > * View Content > * View State > * Change Version > * PG Version > ** Start > ** Commit > ** Force Commit > ** Show changes > ** Revert changes > ** Change Flow version > ** Stop > * Configure PG (NIFI-12417) > * Process Group Services (NIFI-12425) > ** Listing > ** Create > ** Configure > ** Delete > * Configure Processor > ** Service Link > ** Create inline Service > ** Parameter Link > ** Convert to Parameter > * Download Flow > * Create RPG > * Configure RPG > * RPG Remote Ports > * RPG Go To > * Color > * Move to Front > * Copy/Paste > * Run unit tests are part of standard build > * Update all API calls to consider disconnect node confirmation > * Update API
[jira] [Created] (NIFI-12437) Summary page
Rob Fellows created NIFI-12437: -- Summary: Summary page Key: NIFI-12437 URL: https://issues.apache.org/jira/browse/NIFI-12437 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Rob Fellows Assignee: Rob Fellows Build the Summary Page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/29/23 6:07 PM: --- [~iiojj2] Could you possibly still use QueryRecord with Excel reader and not skip the first line (thereby you get your headers), filter out the not needed column(s), write out the csv with the CSVRecordSetWriter and not write out the column names and then read it in again with a CSVReader? was (Author: JIRAUSER294662): [~iiojj2] Could you possibly still use Excel reader and not skip the first line (thereby you get your headers), write out the csv, then use the ReplaceText processor to remove the first line of the columns you do not want and then use CSVReader to read the CSV with the headers you have? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791226#comment-17791226 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] Could you possibly still use Excel reader and not skip the first line (thereby you get your headers), write out the csv, then use the ReplaceText processor to remove the first line of the columns you do not want and then use CSVReader to read the CSV with the headers you have? > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: CSVRecordSetWriter_configuration.png, > ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test > ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png, > image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791207#comment-17791207
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 5:53 PM:
---
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of external data providers and this happens a lot - change
the order of the fields. So to avoid any miscalcs we rely on Field Names as
they come from the file rather than using schemas.
So if we get back to initial problem. I have this data as an Excel file and
trying to use new ExcelReader:
- Infer Schema replaces real columns names - dont want that
- using hardcoded schema is a questionable solution - see my point above
- ExtractSchemaRecord using ExcelReader - returns new column names.
was (Author: iiojj2):
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of external data providers and this happens a lot - change
the order of the fields. So to avoid any miscalcs we rely on Field Names as
they come from the file rather than using schemas.
So if we get back to initial problem. I have this data as an Excel file and
trying to use new ExcelReader:
- Infer Schema replaces real columns names - dont want that
- using hardcoded schema is a questionable solution - see my point above
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791207#comment-17791207
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 5:50 PM:
---
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of external data providers and this happens a lot - change
the order of the fields. So to avoid any miscalcs we rely on Field Names as
they come from the file rather than using schemas.
So if we get back to initial problem. I have this data as an Excel file and
trying to use new ExcelReader:
- Infer Schema replaces real columns names - dont want that
- using hardcoded schema is a questionable solution - see my point above
was (Author: iiojj2):
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of external data providers and this happens a lot - change
the order of the fields. So to avoid any miscalcs we rely on Field Names as
they come from the file rather than using schemas.
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791207#comment-17791207
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 5:34 PM:
---
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of data providers and this happens a lot - change the order
of the fields. So to avoid any miscalcs we rely on Field Names as they come
from the file rather than using schemas.
was (Author: iiojj2):
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791207#comment-17791207
]
Philipp Korniets edited comment on NIFI-11167 at 11/29/23 5:34 PM:
---
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of external data providers and this happens a lot - change
the order of the fields. So to avoid any miscalcs we rely on Field Names as
they come from the file rather than using schemas.
was (Author: iiojj2):
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
We work with a lot of data providers and this happens a lot - change the order
of the fields. So to avoid any miscalcs we rely on Field Names as they come
from the file rather than using schemas.
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12401) Support Parameters in Properties with Allowable Values
[ https://issues.apache.org/jira/browse/NIFI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12401: Fix Version/s: 2.0.0 > Support Parameters in Properties with Allowable Values > -- > > Key: NIFI-12401 > URL: https://issues.apache.org/jira/browse/NIFI-12401 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Update the combo editor to support referencing existing parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[
https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791207#comment-17791207
]
Philipp Korniets commented on NIFI-11167:
-
i might be wrong, but your suggestion has its limitations
i.e. lets assume i have a schema for the above file
{code:java}
{
"type": "record",
"name": "test",
"fields":
[
{"name":"Descr","type":["string","null"]},
{"name":"empty","type":["string","null"]},
{"name":"Events","type":["string","null"]},
{"name":"CostPerEvent","type":["string","null"]},
{"name":"Amount","type":["double","null"]}
]
}
{code}
and my *select statement will be "select sum(Amount) from flowfile *- all works
well.
next - file provider add column before the Amount - column called *MonthlyCost*.
my schema will still work, but the calculation will be based on a completely
different column/values. In the scenario where CSVReader has *Use String Fields
From Header* this will not happen.
> Add Excel Record Reader
> ---
>
> Key: NIFI-11167
> URL: https://issues.apache.org/jira/browse/NIFI-11167
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: David Handermann
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M1, 1.23.0
>
> Attachments: CSVRecordSetWriter_configuration.png,
> ExcelReaderConfiguration.png, QueryRecord_configuration.png, Test
> ExcelReader.xlsx, image-2023-11-28-18-22-07-446.png,
> image-2023-11-29-15-51-08-386.png, resulting.csv, screenshot-1.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX
> spreadsheet rows as NiFi Records. This Reader will enable integration with
> various record-oriented components, obviating the need for the narrowly
> focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader
> should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of
> rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected
> sheets. With Excel supporting typed field values, some amount of field type
> mapping will be required. Additional input filtering properties should not be
> implemented as existing Processors like QueryRecord support a wide variety of
> filtering and projection use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12401) Support Parameters in Properties with Allowable Values
[ https://issues.apache.org/jira/browse/NIFI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12401: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Support Parameters in Properties with Allowable Values > -- > > Key: NIFI-12401 > URL: https://issues.apache.org/jira/browse/NIFI-12401 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Update the combo editor to support referencing existing parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12401) Support Parameters in Properties with Allowable Values
[ https://issues.apache.org/jira/browse/NIFI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791202#comment-17791202 ] ASF subversion and git services commented on NIFI-12401: Commit ebfb5bc12e94563cedeb042a6571e537f99ca3d6 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ebfb5bc12e ] NIFI-12401: Allow combo editor to reference parameters (#8068) * NIFI-12401: - Allow combo editor to reference parameters. * NIFI-12401: - Addressing review feedback. - Handling corner cases where there is no parameter context and where there are no parameters in a bound parameter context. * NIFI-12401: - Fixing formatting issues. This closes #8068 > Support Parameters in Properties with Allowable Values > -- > > Key: NIFI-12401 > URL: https://issues.apache.org/jira/browse/NIFI-12401 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Update the combo editor to support referencing existing parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12401: Allow combo editor to reference parameters [nifi]
rfellows merged PR #8068: URL: https://github.com/apache/nifi/pull/8068 -- 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-12417: Process Group Configuration [nifi]
rfellows commented on code in PR #8075:
URL: https://github.com/apache/nifi/pull/8075#discussion_r1409527869
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/canvas/ui/process-group/edit-process-group/edit-process-group.component.ts:
##
@@ -0,0 +1,227 @@
+/*
+ * 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 { Component, EventEmitter, Inject, Input, Output } from '@angular/core';
+import { MAT_DIALOG_DATA, MatDialogModule } from '@angular/material/dialog';
+import { FormBuilder, FormControl, FormGroup, FormsModule,
ReactiveFormsModule, Validators } from '@angular/forms';
+import { MatInputModule } from '@angular/material/input';
+import { MatCheckboxModule } from '@angular/material/checkbox';
+import { MatButtonModule } from '@angular/material/button';
+import { AsyncPipe, NgForOf, NgIf } from '@angular/common';
+import { MatTabsModule } from '@angular/material/tabs';
+import { MatOptionModule } from '@angular/material/core';
+import { MatSelectModule } from '@angular/material/select';
+import { Observable } from 'rxjs';
+import { SelectOption, TextTipInput } from '../../../../../state/shared';
+import { Client } from '../../../../../service/client.service';
+import { EditComponentDialogRequest } from '../../../state/flow';
+import { PropertyTable } from
'../../../../../ui/common/property-table/property-table.component';
+import { NifiSpinnerDirective } from
'../../../../../ui/common/spinner/nifi-spinner.directive';
+import { NifiTooltipDirective } from
'../../../../../ui/common/tooltips/nifi-tooltip.directive';
+import { TextTip } from
'../../../../../ui/common/tooltips/text-tip/text-tip.component';
+import { ParameterContextEntity } from
'../../../../parameter-contexts/state/parameter-context-listing';
+import { ControllerServiceTable } from
'../../../../../ui/common/controller-service/controller-service-table/controller-service-table.component';
+
+@Component({
+selector: 'edit-process-group',
+standalone: true,
+templateUrl: './edit-process-group.component.html',
+imports: [
+ReactiveFormsModule,
+MatDialogModule,
+MatInputModule,
+MatCheckboxModule,
+MatButtonModule,
+NgIf,
+MatTabsModule,
+MatOptionModule,
+MatSelectModule,
+NgForOf,
+AsyncPipe,
+PropertyTable,
+NifiSpinnerDirective,
+NifiTooltipDirective,
+FormsModule,
+ControllerServiceTable
+],
+styleUrls: ['./edit-process-group.component.scss']
+})
+export class EditProcessGroup {
+@Input() set parameterContexts(parameterContexts:
ParameterContextEntity[]) {
+parameterContexts.forEach((parameterContext) => {
+if (parameterContext.permissions.canRead) {
+this.parameterContextsOptions.push({
+text: parameterContext.component.name,
+value: parameterContext.id,
+description: parameterContext.component.description
+});
+}
+});
+
+if (this.request.entity.component.parameterContext) {
+this.editProcessGroupForm.addControl(
+'parameterContext',
+new
FormControl(this.request.entity.component.parameterContext.id)
+);
+} else {
+this.editProcessGroupForm.addControl('parameterContext', new
FormControl(null));
+}
+}
+@Input() saving$!: Observable;
+@Output() editProcessGroup: EventEmitter = new EventEmitter();
+
+protected readonly TextTip = TextTip;
+
+editProcessGroupForm: FormGroup;
+parameterContextsOptions: SelectOption[] = [];
+
+executionEngineOptions: SelectOption[] = [
+{
+text: 'Inherited',
+value: 'INHERITED',
+description: 'Use whichever Execution Engine the parent Process
Group is configured to use.'
+},
+{
+text: 'Standard',
+value: 'STANDARD',
+description: 'Use the Standard NiFi Execution Engine. See the User
Guide for additional details.'
+},
+{
+text: 'Stateless',
+
[jira] [Updated] (NIFI-12434) Upgrade Spring Framework to 6.1.1 and Spring Boot to 3.2.0 for Registry
[ https://issues.apache.org/jira/browse/NIFI-12434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12434: Summary: Upgrade Spring Framework to 6.1.1 and Spring Boot to 3.2.0 for Registry (was: Upgrade Spring Framework to 6.1.0 and Spring Boot to 3.2.0 for Registry) > Upgrade Spring Framework to 6.1.1 and Spring Boot to 3.2.0 for Registry > --- > > Key: NIFI-12434 > URL: https://issues.apache.org/jira/browse/NIFI-12434 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > > Following the release of Spring Framework 6.1.0 and Spring Boot 3.2.0, NiFi > Registry should be upgraded to the latest framework versions, along with > transitive dependencies. > This upgrade should cover the same components as the earlier upgrade to > Spring Framework 6.0.13 for Registry, and separate issues will be used to > track upgrading NiFi and remaining application components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12436 Update datafaker to 2.0.2 [nifi]
mr1716 opened a new pull request, #8084: URL: https://github.com/apache/nifi/pull/8084 # Summary [NIFI-12436](https://issues.apache.org/jira/browse/NIFI-12436) # 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-12436) 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12436) Update datafaker to 2.0.2
[ https://issues.apache.org/jira/browse/NIFI-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12436: - Assignee: Mike R > Update datafaker to 2.0.2 > - > > Key: NIFI-12436 > URL: https://issues.apache.org/jira/browse/NIFI-12436 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update datafaker to 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12436) Update datafaker to 2.0.2
Mike R created NIFI-12436: - Summary: Update datafaker to 2.0.2 Key: NIFI-12436 URL: https://issues.apache.org/jira/browse/NIFI-12436 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M1 Reporter: Mike R Update datafaker to 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12428) Create Enforcer rule for max Java version on 1.X branch
[
https://issues.apache.org/jira/browse/NIFI-12428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz reassigned NIFI-12428:
---
Assignee: Daniel Stieglitz
> Create Enforcer rule for max Java version on 1.X branch
> ---
>
> Key: NIFI-12428
> URL: https://issues.apache.org/jira/browse/NIFI-12428
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 1.25.0
>
>
> I found it is possible to attempt to build the 1.x branch with Java 21
> although the build fails at /nifi-commons/nifi-hl7-query-language
> with error message
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile
> (default-compile) on project nifi-hl7-query-language: Compilation failure:
> Compilation failure:
> [ERROR] error: Source option 7 is no longer supported. Use 8 or later.
> [ERROR] error: Target option 7 is no longer supported. Use 8 or later.
> {quote}
>
> There should be an enforcer rule on the maximum Java version (17) which can
> be used to prevent this. Currently there is only an enforcer rule on the
> minimum version 1.8 (version specified in the NIFI pom.xml as a property and
> the enforcer rule inherited from the Apache parent pom.xml).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12435 Update QuestDB to 7.3.5 [nifi]
mr1716 opened a new pull request, #8083: URL: https://github.com/apache/nifi/pull/8083 # Summary [NIFI-12435](https://issues.apache.org/jira/browse/NIFI-12435) # 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-12435) 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12435) Update QuestDB to 7.3.5
[ https://issues.apache.org/jira/browse/NIFI-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12435: - Assignee: Mike R > Update QuestDB to 7.3.5 > --- > > Key: NIFI-12435 > URL: https://issues.apache.org/jira/browse/NIFI-12435 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update QuestDB to 7.3.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12435) Update QuestDB to 7.3.5
Mike R created NIFI-12435: - Summary: Update QuestDB to 7.3.5 Key: NIFI-12435 URL: https://issues.apache.org/jira/browse/NIFI-12435 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M1 Reporter: Mike R Update QuestDB to 7.3.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12434) Upgrade Spring Framework to 6.1.0 and Spring Boot to 3.2.0 for Registry
David Handermann created NIFI-12434: --- Summary: Upgrade Spring Framework to 6.1.0 and Spring Boot to 3.2.0 for Registry Key: NIFI-12434 URL: https://issues.apache.org/jira/browse/NIFI-12434 Project: Apache NiFi Issue Type: Improvement Components: NiFi Registry Reporter: David Handermann Assignee: David Handermann Following the release of Spring Framework 6.1.0 and Spring Boot 3.2.0, NiFi Registry should be upgraded to the latest framework versions, along with transitive dependencies. This upgrade should cover the same components as the earlier upgrade to Spring Framework 6.0.13 for Registry, and separate issues will be used to track upgrading NiFi and remaining application components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12433 Update mariadb-java-client to 3.3.0 [nifi]
mr1716 opened a new pull request, #8082: URL: https://github.com/apache/nifi/pull/8082 # Summary [NIFI-12433](https://issues.apache.org/jira/browse/NIFI-12433) # 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-12433) 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12433) Update mariadb-java-client to 3.3.0
Mike R created NIFI-12433: - Summary: Update mariadb-java-client to 3.3.0 Key: NIFI-12433 URL: https://issues.apache.org/jira/browse/NIFI-12433 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.24.0, 2.0.0-M1 Reporter: Mike R Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12433) Update mariadb-java-client to 3.3.0
[ https://issues.apache.org/jira/browse/NIFI-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12433: - Assignee: Mike R > Update mariadb-java-client to 3.3.0 > --- > > Key: NIFI-12433 > URL: https://issues.apache.org/jira/browse/NIFI-12433 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update mariadb-java-client to 3.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12432) Update spring.version to 5.3.31
[ https://issues.apache.org/jira/browse/NIFI-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12432: - Assignee: Mike R > Update spring.version to 5.3.31 > --- > > Key: NIFI-12432 > URL: https://issues.apache.org/jira/browse/NIFI-12432 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update spring.version to 5.3.31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12429 Update spring.boot.version to 3.1.6 [nifi]
mr1716 closed pull request #8079: NIFI-12429 Update spring.boot.version to 3.1.6 URL: https://github.com/apache/nifi/pull/8079 -- 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-12429) Update spring.boot.version to 3.1.6
[ https://issues.apache.org/jira/browse/NIFI-12429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R resolved NIFI-12429. --- Resolution: Won't Fix Will fix later to newer version > Update spring.boot.version to 3.1.6 > --- > > Key: NIFI-12429 > URL: https://issues.apache.org/jira/browse/NIFI-12429 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Update spring.boot.version to 3.1.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12429 Update spring.boot.version to 3.1.6 [nifi]
mr1716 commented on PR #8079: URL: https://github.com/apache/nifi/pull/8079#issuecomment-1832227937 @exceptionfactory that makes sense. Lets close this ticket -- 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
