[jira] [Updated] (NIFI-10941) Remove TestNG
[
https://issues.apache.org/jira/browse/NIFI-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-10941:
Status: Patch Available (was: Open)
> Remove TestNG
> -
>
> Key: NIFI-10941
> URL: https://issues.apache.org/jira/browse/NIFI-10941
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Several tests in {{nifi-framework-bundle}} reference TestNG assertions
> instead of JUnit assertions, and several {{nifi-toolkit}} modules include
> TestNG transitive dependencies through {{groovy-all}}. All test references
> should be converted to JUnit 5, and TestNG should be excluded from all
> modules to avoid inadvertent references.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] exceptionfactory opened a new pull request, #6753: NIFI-10941 Remove TestNG references
exceptionfactory opened a new pull request, #6753: URL: https://github.com/apache/nifi/pull/6753 # Summary [NIFI-10941](https://issues.apache.org/jira/browse/NIFI-10941) Removes all references to TestNG assertions and dependencies. Several test classes had inadvertent references to TestNG assertions, which should be using JUnit, and several Toolkit modules included TestNG dependencies through Groovy. Changes include refactoring impacted tests to use JUnit 5 and adding TestNG to the list of banned dependencies. # 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 8 - [ ] JDK 11 - [ ] JDK 17 ### 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-10941) Remove TestNG
David Handermann created NIFI-10941:
---
Summary: Remove TestNG
Key: NIFI-10941
URL: https://issues.apache.org/jira/browse/NIFI-10941
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework, Tools and Build
Reporter: David Handermann
Assignee: David Handermann
Several tests in {{nifi-framework-bundle}} reference TestNG assertions instead
of JUnit assertions, and several {{nifi-toolkit}} modules include TestNG
transitive dependencies through {{groovy-all}}. All test references should be
converted to JUnit 5, and TestNG should be excluded from all modules to avoid
inadvertent references.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9598) Load Balancing on labeled nodes and/or fixed amount of usable nodes in process groups
[ https://issues.apache.org/jira/browse/NIFI-9598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642883#comment-17642883 ] Denis Jakupovic commented on NIFI-9598: --- Any news on this? > Load Balancing on labeled nodes and/or fixed amount of usable nodes in > process groups > - > > Key: NIFI-9598 > URL: https://issues.apache.org/jira/browse/NIFI-9598 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.15.3 >Reporter: Denis Jakupovic >Priority: Trivial > > One of NiFi's great features is its linear scalability by adding just more > nodes. However by only having the distribute load processor or by round > robin, load balance by attribute name or to a single node feature in the > connection, we could need a more granular form of distributing flowfiles > through the cluster. > Let's assume we have a 10 node NiFi Cluster. > Round Robin: Each node would get 1/10 of the flowfiles. > Single Node: Only one node would process all FF. Chance that other process > groups distribute to same node is 1/10 > By Attribute: 1-10 nodes could get the data, not evenly partitioned > Distribute Load Processor: Manual and fixed process, cannot scale with adding > more nodes to the cluster and needs > By having several dataflows with different use cases with enormous variance > in computation, one or a few dataflows can slow down all other data flows. > Therefore a solution could be partitioning the data to labeled nodes or by > setting the maximum allowed nodes to use for FF partitioning/load balancing > on process groups or a connection. > In the cluster configuration each node could be labeled. Distributing the FF > by round robin would only be distributed to the labeled nodes with the proper > label. A distribution by attribute name would mean to build the attribute > accordingly and cannot be build dynamically. > Another great feature would be the maximum amount of nodes a process group > can use to distribute nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-9889) client.rack for kafka consumer processors
[ https://issues.apache.org/jira/browse/NIFI-9889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642882#comment-17642882 ] Denis Jakupovic commented on NIFI-9889: --- Any news on this? > client.rack for kafka consumer processors > - > > Key: NIFI-9889 > URL: https://issues.apache.org/jira/browse/NIFI-9889 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.15.3 >Reporter: Denis Jakupovic >Priority: Trivial > > Hey, > it woul be great if the kafka consumer processors would have an attribtue for > the rack.id/client.rack of a kafka cluster/rack to fetch the follower > partitions from one rack instead of reading from each leader of different > racks. > Since Kafka 2.4 the RackAwareReplicaSelector is available and through the > client.rack as a consumer each partitions of one rack can be read for > performance considerations e.g. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-9643) executeSQL processor now needs an incomming connection if set on primary node execution
[ https://issues.apache.org/jira/browse/NIFI-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Jakupovic resolved NIFI-9643. --- Resolution: Fixed > executeSQL processor now needs an incomming connection if set on primary node > execution > --- > > Key: NIFI-9643 > URL: https://issues.apache.org/jira/browse/NIFI-9643 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.15.3 >Reporter: Denis Jakupovic >Priority: Minor > > By updating nifi to the current 1.15.3 version, the executesql processor > which was scheduled every n seconds need now an incomming connection if set > on primary node execution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10940) Delete single FlowFile from queues
Denis Jakupovic created NIFI-10940: -- Summary: Delete single FlowFile from queues Key: NIFI-10940 URL: https://issues.apache.org/jira/browse/NIFI-10940 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.19.0 Reporter: Denis Jakupovic Hey, the NiFi UI has no feature of removing FlowFiles from a queue through "List Queue". Best would be single deletion and "delete all selected" where a search filter can be applied, e.g. search for FlowFiles in Queue through attributes and delete all at once or by checkboxes Thank you in advance -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi-fds] dependabot[bot] opened a new pull request, #71: Bump decode-uri-component from 0.2.0 to 0.2.2
dependabot[bot] opened a new pull request, #71: URL: https://github.com/apache/nifi-fds/pull/71 Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. Release notes Sourced from https://github.com/SamVerschueren/decode-uri-component/releases;>decode-uri-component's releases. v0.2.2 Prevent overwriting previously decoded tokens 980e0bf https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2;>https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2 v0.2.1 Switch to GitHub workflows 76abc93 Fix issue where decode throws - fixes https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/6;>#6 746ca5d Update license (https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/1;>#1) 486d7e2 Tidelift tasks a650457 Meta tweaks 66e1c28 https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1;>https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1 Commits https://github.com/SamVerschueren/decode-uri-component/commit/a0eea469d26eb0df668b081672cdb9581feb78eb;>a0eea46 0.2.2 https://github.com/SamVerschueren/decode-uri-component/commit/980e0bf09b64d94f1aa79012f895816c30ffd152;>980e0bf Prevent overwriting previously decoded tokens https://github.com/SamVerschueren/decode-uri-component/commit/3c8a373dd4837e89b3f970e01295dd03e1405a33;>3c8a373 0.2.1 https://github.com/SamVerschueren/decode-uri-component/commit/76abc939783fe3900fadb7d384a74d324d5557f3;>76abc93 Switch to GitHub workflows https://github.com/SamVerschueren/decode-uri-component/commit/746ca5dcb6667c5d364e782d53c542830e4c10b9;>746ca5d Fix issue where decode throws - fixes https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/6;>#6 https://github.com/SamVerschueren/decode-uri-component/commit/486d7e26d3a8c0fbe860fb651fe1bc98c2f2be30;>486d7e2 Update license (https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/1;>#1) https://github.com/SamVerschueren/decode-uri-component/commit/a65045724e6234acef87f31da499d4807b20b134;>a650457 Tidelift tasks https://github.com/SamVerschueren/decode-uri-component/commit/66e1c2834c0e189201cb65196ec3101372459b02;>66e1c28 Meta tweaks See full diff in https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.2;>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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts
