[GitHub] [nifi] abdelrahim-ahmad commented on pull request #6368: NIFI-10442: Create PutIceberg processor
abdelrahim-ahmad commented on PR #6368: URL: https://github.com/apache/nifi/pull/6368#issuecomment-1480364703 Thank you very much, I was not aware of the NARs project. Is there any chance for this to be included in the upcoming versions by default? or It will stays in NARs. -- 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-11302) Fix version info in About dialog for NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703807#comment-17703807 ] ASF subversion and git services commented on NIFI-11302: Commit e27396e7c0141de025841531e08c1c3ec80d6add in nifi's branch refs/heads/support/nifi-1.x from Mark Bean [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e27396e7c0 ] NIFI-11302 Corrected Registry version retrieval - Updated Maven JAR plugin configuration for nifi-registry-data-model to include implementation version This closes #7057 Co-authored-by: David Handermann Signed-off-by: David Handermann > Fix version info in About dialog for NiFi Registry > -- > > Key: NIFI-11302 > URL: https://issues.apache.org/jira/browse/NIFI-11302 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > The About dialog for NiFi Registry does not display the version information > when using Java 11; it only works for Java 8. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11302) Fix version info in About dialog for NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11302: Fix Version/s: 2.0.0 1.21.0 1.latest 2.latest Resolution: Fixed Status: Resolved (was: Patch Available) > Fix version info in About dialog for NiFi Registry > -- > > Key: NIFI-11302 > URL: https://issues.apache.org/jira/browse/NIFI-11302 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Fix For: 2.0.0, 1.21.0, 1.latest, 2.latest > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The About dialog for NiFi Registry does not display the version information > when using Java 11; it only works for Java 8. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11302) Fix version info in About dialog for NiFi Registry
[ https://issues.apache.org/jira/browse/NIFI-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703806#comment-17703806 ] ASF subversion and git services commented on NIFI-11302: Commit af3737e6705ee9c0cbadbc558f4c9bd066c05500 in nifi's branch refs/heads/main from Mark Bean [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=af3737e670 ] NIFI-11302 Corrected Registry version retrieval - Updated Maven JAR plugin configuration for nifi-registry-data-model to include implementation version This closes #7057 Co-authored-by: David Handermann Signed-off-by: David Handermann > Fix version info in About dialog for NiFi Registry > -- > > Key: NIFI-11302 > URL: https://issues.apache.org/jira/browse/NIFI-11302 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > The About dialog for NiFi Registry does not display the version information > when using Java 11; it only works for Java 8. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7057: NIFI-11302: add Registry version to About dialog fixing bug for Java 11
exceptionfactory closed pull request #7057: NIFI-11302: add Registry version to About dialog fixing bug for Java 11 URL: https://github.com/apache/nifi/pull/7057 -- 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
[GitHub] [nifi] dependabot[bot] opened a new pull request, #7075: Bump jettison from 1.5.2 to 1.5.4 in /nifi-nar-bundles/nifi-framework-bundle
dependabot[bot] opened a new pull request, #7075: URL: https://github.com/apache/nifi/pull/7075 Bumps [jettison](https://github.com/jettison-json/jettison) from 1.5.2 to 1.5.4. Release notes Sourced from https://github.com/jettison-json/jettison/releases;>jettison's releases. Jettison 1.5.4 What's Changed Fixing issue 60 by https://github.com/coheigea;>@coheigea in https://redirect.github.com/jettison-json/jettison/pull/62;>jettison-json/jettison#62 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4;>https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4 Jettison 1.5.3 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3;>https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3 Commits https://github.com/jettison-json/jettison/commit/a77ffc4a70e91945603f4947828cd7d4633a3cdb;>a77ffc4 [maven-release-plugin] prepare release jettison-1.5.4 https://github.com/jettison-json/jettison/commit/c20a8be23f698d7d89b7ccf8d328971cf4709b9f;>c20a8be Fixing issue 60 https://github.com/jettison-json/jettison/commit/3e1a913eaeda4bbebc972a731330d8f697eba95c;>3e1a913 [maven-release-plugin] prepare for next development iteration https://github.com/jettison-json/jettison/commit/da6d8bc48a1f5d840ad54b3269297f6636f41f04;>da6d8bc [maven-release-plugin] prepare release jettison-1.5.3 https://github.com/jettison-json/jettison/commit/9e3ec6fe002f635c11f2d7ae5f04c722e2771406;>9e3ec6f Remove commented out code https://github.com/jettison-json/jettison/commit/b3c40001b92f5153ace0687e4ef6fb488d655d0c;>b3c4000 Adding another test for backslashes https://github.com/jettison-json/jettison/commit/631c21e9c467c310a22f5276a2ee0f1aa65359ce;>631c21e Try and fix backslash escaping. Throw syntax exception on invalid json sooner https://github.com/jettison-json/jettison/commit/d9da8084b221dfbc8752e35e006c10ca468dc9d7;>d9da808 Introducing new static methods to set the recursion depth limit https://github.com/jettison-json/jettison/commit/888eec8ea8ef97c0d01a86550589ee7c81896f45;>888eec8 Incorrect recursion depth check in JSONTokener https://github.com/jettison-json/jettison/commit/677aba586094fafbf53f7588aec6218d93933997;>677aba5 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.4;>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) 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
[GitHub] [nifi] dependabot[bot] opened a new pull request, #7074: Bump jettison from 1.5.2 to 1.5.4 in /nifi-nar-bundles/nifi-spark-bundle
dependabot[bot] opened a new pull request, #7074: URL: https://github.com/apache/nifi/pull/7074 Bumps [jettison](https://github.com/jettison-json/jettison) from 1.5.2 to 1.5.4. Release notes Sourced from https://github.com/jettison-json/jettison/releases;>jettison's releases. Jettison 1.5.4 What's Changed Fixing issue 60 by https://github.com/coheigea;>@coheigea in https://redirect.github.com/jettison-json/jettison/pull/62;>jettison-json/jettison#62 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4;>https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4 Jettison 1.5.3 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3;>https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3 Commits https://github.com/jettison-json/jettison/commit/a77ffc4a70e91945603f4947828cd7d4633a3cdb;>a77ffc4 [maven-release-plugin] prepare release jettison-1.5.4 https://github.com/jettison-json/jettison/commit/c20a8be23f698d7d89b7ccf8d328971cf4709b9f;>c20a8be Fixing issue 60 https://github.com/jettison-json/jettison/commit/3e1a913eaeda4bbebc972a731330d8f697eba95c;>3e1a913 [maven-release-plugin] prepare for next development iteration https://github.com/jettison-json/jettison/commit/da6d8bc48a1f5d840ad54b3269297f6636f41f04;>da6d8bc [maven-release-plugin] prepare release jettison-1.5.3 https://github.com/jettison-json/jettison/commit/9e3ec6fe002f635c11f2d7ae5f04c722e2771406;>9e3ec6f Remove commented out code https://github.com/jettison-json/jettison/commit/b3c40001b92f5153ace0687e4ef6fb488d655d0c;>b3c4000 Adding another test for backslashes https://github.com/jettison-json/jettison/commit/631c21e9c467c310a22f5276a2ee0f1aa65359ce;>631c21e Try and fix backslash escaping. Throw syntax exception on invalid json sooner https://github.com/jettison-json/jettison/commit/d9da8084b221dfbc8752e35e006c10ca468dc9d7;>d9da808 Introducing new static methods to set the recursion depth limit https://github.com/jettison-json/jettison/commit/888eec8ea8ef97c0d01a86550589ee7c81896f45;>888eec8 Incorrect recursion depth check in JSONTokener https://github.com/jettison-json/jettison/commit/677aba586094fafbf53f7588aec6218d93933997;>677aba5 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.4;>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) 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
[GitHub] [nifi] dependabot[bot] opened a new pull request, #7073: Bump jettison from 1.5.2 to 1.5.4 in /nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin
dependabot[bot] opened a new pull request, #7073: URL: https://github.com/apache/nifi/pull/7073 Bumps [jettison](https://github.com/jettison-json/jettison) from 1.5.2 to 1.5.4. Release notes Sourced from https://github.com/jettison-json/jettison/releases;>jettison's releases. Jettison 1.5.4 What's Changed Fixing issue 60 by https://github.com/coheigea;>@coheigea in https://redirect.github.com/jettison-json/jettison/pull/62;>jettison-json/jettison#62 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4;>https://github.com/jettison-json/jettison/compare/jettison-1.5.3...jettison-1.5.4 Jettison 1.5.3 Full Changelog: https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3;>https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.3 Commits https://github.com/jettison-json/jettison/commit/a77ffc4a70e91945603f4947828cd7d4633a3cdb;>a77ffc4 [maven-release-plugin] prepare release jettison-1.5.4 https://github.com/jettison-json/jettison/commit/c20a8be23f698d7d89b7ccf8d328971cf4709b9f;>c20a8be Fixing issue 60 https://github.com/jettison-json/jettison/commit/3e1a913eaeda4bbebc972a731330d8f697eba95c;>3e1a913 [maven-release-plugin] prepare for next development iteration https://github.com/jettison-json/jettison/commit/da6d8bc48a1f5d840ad54b3269297f6636f41f04;>da6d8bc [maven-release-plugin] prepare release jettison-1.5.3 https://github.com/jettison-json/jettison/commit/9e3ec6fe002f635c11f2d7ae5f04c722e2771406;>9e3ec6f Remove commented out code https://github.com/jettison-json/jettison/commit/b3c40001b92f5153ace0687e4ef6fb488d655d0c;>b3c4000 Adding another test for backslashes https://github.com/jettison-json/jettison/commit/631c21e9c467c310a22f5276a2ee0f1aa65359ce;>631c21e Try and fix backslash escaping. Throw syntax exception on invalid json sooner https://github.com/jettison-json/jettison/commit/d9da8084b221dfbc8752e35e006c10ca468dc9d7;>d9da808 Introducing new static methods to set the recursion depth limit https://github.com/jettison-json/jettison/commit/888eec8ea8ef97c0d01a86550589ee7c81896f45;>888eec8 Incorrect recursion depth check in JSONTokener https://github.com/jettison-json/jettison/commit/677aba586094fafbf53f7588aec6218d93933997;>677aba5 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/jettison-json/jettison/compare/jettison-1.5.2...jettison-1.5.4;>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) 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
[GitHub] [nifi] emiliosetiadarma opened a new pull request, #7072: NIFI-9196: changed to use Strings instead of the File class for movin…
emiliosetiadarma opened a new pull request, #7072: URL: https://github.com/apache/nifi/pull/7072 …g files as part of the move file completion strategy for FetchSFTP # Summary [NIFI-9196](https://issues.apache.org/jira/browse/NIFI-9196) # 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` - [] JDK 11 - [x] 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] [Resolved] (NIFI-11319) Fixing TestStatelessBootstrap::testClassNotAllowed
[ https://issues.apache.org/jira/browse/NIFI-11319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-11319. --- Fix Version/s: 2.0.0 1.21.0 Resolution: Fixed > Fixing TestStatelessBootstrap::testClassNotAllowed > -- > > Key: NIFI-11319 > URL: https://issues.apache.org/jira/browse/NIFI-11319 > Project: Apache NiFi > Issue Type: Bug > Components: NiFi Stateless >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > "TestStatelessBootstrap::testClassNotAllowed" is broken due to the given > class is part of the allowed list. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11319) Fixing TestStatelessBootstrap::testClassNotAllowed
[ https://issues.apache.org/jira/browse/NIFI-11319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703785#comment-17703785 ] ASF subversion and git services commented on NIFI-11319: Commit cef61c866d80816a93b1836e700acc5d3f249c5e in nifi's branch refs/heads/support/nifi-1.x from simonbence [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cef61c866d ] NIFI-11319 Fixing TestStatelessBootstrap::testClassNotAllowed (#7070) > Fixing TestStatelessBootstrap::testClassNotAllowed > -- > > Key: NIFI-11319 > URL: https://issues.apache.org/jira/browse/NIFI-11319 > Project: Apache NiFi > Issue Type: Bug > Components: NiFi Stateless >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > "TestStatelessBootstrap::testClassNotAllowed" is broken due to the given > class is part of the allowed list. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] markap14 commented on pull request #7070: NIFI-11319 Fixing TestStatelessBootstrap::testClassNotAllowed
markap14 commented on PR #7070: URL: https://github.com/apache/nifi/pull/7070#issuecomment-1480214797 Thanks @simonbence that does appear to address the issue. Interestingly, I didn't encounter it when running `mvn clean install` because all of the directories under `target` hadn't yet been completed when that runs. But if you run in the IDE after building or run via `mvn test` after the build has completed, it failed. +1 merged to main and support branches -- 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-11319) Fixing TestStatelessBootstrap::testClassNotAllowed
[ https://issues.apache.org/jira/browse/NIFI-11319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703784#comment-17703784 ] ASF subversion and git services commented on NIFI-11319: Commit f062b0d1f1e39c869fe2632d5412012a56c3e4f8 in nifi's branch refs/heads/main from simonbence [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f062b0d1f1 ] NIFI-11319 Fixing TestStatelessBootstrap::testClassNotAllowed (#7070) > Fixing TestStatelessBootstrap::testClassNotAllowed > -- > > Key: NIFI-11319 > URL: https://issues.apache.org/jira/browse/NIFI-11319 > Project: Apache NiFi > Issue Type: Bug > Components: NiFi Stateless >Reporter: Simon Bence >Assignee: Simon Bence >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > "TestStatelessBootstrap::testClassNotAllowed" is broken due to the given > class is part of the allowed list. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] markap14 merged pull request #7070: NIFI-11319 Fixing TestStatelessBootstrap::testClassNotAllowed
markap14 merged PR #7070: URL: https://github.com/apache/nifi/pull/7070 -- 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-10976) Add Migration Capabilities from ZooKeeper to Kubernetes
[ https://issues.apache.org/jira/browse/NIFI-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann reassigned NIFI-10976: --- Assignee: David Handermann > Add Migration Capabilities from ZooKeeper to Kubernetes > --- > > Key: NIFI-10976 > URL: https://issues.apache.org/jira/browse/NIFI-10976 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > > Following initial implementation for the Kubernetes State Provider, migration > tools should be created to read from ZooKeeper and write to Kubernetes > ConfigMaps. This should facilitate moving existing deployments from ZooKeeper > to Kubernetes while preserving cluster state information. The existing > ZooKeeper migrator provides a basis for the implementation, but additional > work will be necessary to support TLS connections to ZooKeeper. Refactoring > the current implementation for more intuitive command design, as support for > configurable destinations may be required. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] abdelrahim-ahmad commented on pull request #6368: NIFI-10442: Create PutIceberg processor
abdelrahim-ahmad commented on PR #6368: URL: https://github.com/apache/nifi/pull/6368#issuecomment-1480050425 Hi Guys, thanks for this great feature. I've installed nifi 1.20.0 but not able to find this new process PutIceberg ? why is that? is there any thing I should consider!? -- 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-11322) ClusterSynchronization errors
[ https://issues.apache.org/jira/browse/NIFI-11322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Lord updated NIFI-11322: - Attachment: App.log events.txt > ClusterSynchronization errors > - > > Key: NIFI-11322 > URL: https://issues.apache.org/jira/browse/NIFI-11322 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.19.1 >Reporter: Phil Lord >Priority: Major > Attachments: App.log events.txt, StackTraceFromUser.log > > > Environment: Small 3-node cluster; 4GB Heap/4 Cores per node > See attachments referencing errors in both user.log and corresponding > app.log. I'm not sure if these errors might be resolved in some of the > tickets being addressed in 1.21.0? The only resolution was a restart of the > node... attempts to re-sync the node through a UI level connection request > failed. Of note the errors were seen within a Registry versioned > ProcessGroup. > 2023-03-21 02:43:16,574 INFO [Reconnect to Cluster] > o.a.nifi.controller.StandardFlowService Node disconnected due to Failed to > properly handle Reconnection request due to > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > 2023-03-21 02:43:16,574 ERROR [Reconnect to Cluster] > o.a.nifi.controller.StandardFlowService Handling reconnection request failed > due to: > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059) > at > org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667) > at > org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107) > at > org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396) > at java.base/java.lang.Thread.run(Thread.java:829) > Caused by: > org.apache.nifi.controller.serialization.FlowSynchronizationException: > java.lang.IllegalStateException: Upstream component of Connection > (PutS3Object[id=9fcf34ef-d59e-16bc-9e3c-7c619c5e40af]) is running > at > org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:447) > at > org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:205) > at > org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42) > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1525) > at > org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104) > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817) > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1028) > ... 4 common frames omitted > Caused by: java.lang.IllegalStateException: Upstream component of Connection > (PutS3Object[id=9fcf34ef-d59e-16bc-9e3c-7c619c5e40af]) is running > at > org.apache.nifi.connectable.StandardConnection.verifySourceStoppedOrFunnel(StandardConnection.java:529) > at > org.apache.nifi.connectable.StandardConnection.verifyCanDelete(StandardConnection.java:510) > at > org.apache.nifi.groups.StandardProcessGroup.removeConnection(StandardProcessGroup.java:1375) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.removeMissingConnections(StandardVersionedComponentSynchronizer.java:619) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:383) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:537) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:411) > at >
[jira] [Updated] (NIFI-11322) ClusterSynchronization errors
[ https://issues.apache.org/jira/browse/NIFI-11322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Lord updated NIFI-11322: - Attachment: (was: CorrespondingApp.log) > ClusterSynchronization errors > - > > Key: NIFI-11322 > URL: https://issues.apache.org/jira/browse/NIFI-11322 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.19.1 >Reporter: Phil Lord >Priority: Major > Attachments: StackTraceFromUser.log > > > Environment: Small 3-node cluster; 4GB Heap/4 Cores per node > See attachments referencing errors in both user.log and corresponding > app.log. I'm not sure if these errors might be resolved in some of the > tickets being addressed in 1.21.0? The only resolution was a restart of the > node... attempts to re-sync the node through a UI level connection request > failed. Of note the errors were seen within a Registry versioned > ProcessGroup. > 2023-03-21 02:43:16,574 INFO [Reconnect to Cluster] > o.a.nifi.controller.StandardFlowService Node disconnected due to Failed to > properly handle Reconnection request due to > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > 2023-03-21 02:43:16,574 ERROR [Reconnect to Cluster] > o.a.nifi.controller.StandardFlowService Handling reconnection request failed > due to: > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed > to connect node to cluster because local flow controller partially updated. > Administrator should disconnect node and review flow for corruption. > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1059) > at > org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:667) > at > org.apache.nifi.controller.StandardFlowService.access$200(StandardFlowService.java:107) > at > org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:396) > at java.base/java.lang.Thread.run(Thread.java:829) > Caused by: > org.apache.nifi.controller.serialization.FlowSynchronizationException: > java.lang.IllegalStateException: Upstream component of Connection > (PutS3Object[id=9fcf34ef-d59e-16bc-9e3c-7c619c5e40af]) is running > at > org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.synchronizeFlow(VersionedFlowSynchronizer.java:447) > at > org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:205) > at > org.apache.nifi.controller.serialization.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:42) > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1525) > at > org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:104) > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817) > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1028) > ... 4 common frames omitted > Caused by: java.lang.IllegalStateException: Upstream component of Connection > (PutS3Object[id=9fcf34ef-d59e-16bc-9e3c-7c619c5e40af]) is running > at > org.apache.nifi.connectable.StandardConnection.verifySourceStoppedOrFunnel(StandardConnection.java:529) > at > org.apache.nifi.connectable.StandardConnection.verifyCanDelete(StandardConnection.java:510) > at > org.apache.nifi.groups.StandardProcessGroup.removeConnection(StandardProcessGroup.java:1375) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.removeMissingConnections(StandardVersionedComponentSynchronizer.java:619) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:383) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:537) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:411) > at > org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:255)
[GitHub] [nifi] kevdoran commented on pull request #6995: NIFI-7060 populate NiFi and NiFi Registry properties files using env vars in Docker Containers
kevdoran commented on PR #6995: URL: https://github.com/apache/nifi/pull/6995#issuecomment-1479889891 Hi @exceptionfactory @ChrisSamo632 - Sorry I missed this PR initially, and then I've been out sick recently. I'm going to try to ramp up on this set of changes so I can help with reviews. Regarding - [NIFI-11315](https://issues.apache.org/jira/browse/NIFI-11315) for general environment variable configuration of applications I did look into this a while back. I agree that moving this capability into NiFi application code itself would be the most robust. Some searches showed that it might be be possible to use SpringBoot's `ConfigurationProperties` library without using SpringBoot, but that would probably be too big a lift. It's an option, but maybe we could implement our own solution. I'll try to comment on the Jira. -- 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
[GitHub] [nifi-minifi-cpp] lordgamez commented on a diff in pull request #1530: MINIFICPP-2018 Add ProcessContext::getStateManager to Lua/Python
lordgamez commented on code in PR #1530:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1530#discussion_r1145095082
##
extensions/python/types/PyStateManager.cpp:
##
@@ -0,0 +1,103 @@
+/**
+ * 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,
+a * 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.
+ */
+
+#include "PyStateManager.h"
+#include
+#include "PyException.h"
+
+extern "C" {
+namespace org::apache::nifi::minifi::extensions::python {
+
+static PyMethodDef PyStateManager_methods[] = {
Review Comment:
Thanks for the clarification!
--
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
[GitHub] [nifi] exceptionfactory opened a new pull request, #7071: NIFI-11325 Upgraded Mockito from 3.12.4 to 4.11.0
exceptionfactory opened a new pull request, #7071: URL: https://github.com/apache/nifi/pull/7071 # Summary [NIFI-11325](https://issues.apache.org/jira/browse/NIFI-11325) Upgrades Mockito from 3.12.4 to [4.11.0](https://github.com/mockito/mockito/releases/tag/v4.11.0) and updates deprecated references to current methods. [Mockito 4](https://github.com/mockito/mockito/releases/tag/v4.0.0) provides the current baseline version for Java 8, which works for both the NiFi current main branch and the support branch. Subsequent efforts can evaluate upgrading the main branch to Mockito 5, which requires Java 11. # 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 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] [Updated] (NIFI-11325) Upgrade Mockito to 4.11.0
[ https://issues.apache.org/jira/browse/NIFI-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-11325: Fix Version/s: 1.latest 2.latest Status: Patch Available (was: Open) > Upgrade Mockito to 4.11.0 > - > > Key: NIFI-11325 > URL: https://issues.apache.org/jira/browse/NIFI-11325 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Mockito [4.0.0|https://github.com/mockito/mockito/releases/tag/v4.0.0] > removes several deprecated components and provides a baseline of support for > Java 8. > Mockito should be upgraded from version 3 to the latest version 4 on both > main and support branches, and then the main branch can be evaluated for > upgrade to Mockito 5, which requires Java 11 as the minimum version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11325) Upgrade Mockito to 4.11.0
David Handermann created NIFI-11325: --- Summary: Upgrade Mockito to 4.11.0 Key: NIFI-11325 URL: https://issues.apache.org/jira/browse/NIFI-11325 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: David Handermann Assignee: David Handermann Mockito [4.0.0|https://github.com/mockito/mockito/releases/tag/v4.0.0] removes several deprecated components and provides a baseline of support for Java 8. Mockito should be upgraded from version 3 to the latest version 4 on both main and support branches, and then the main branch can be evaluated for upgrade to Mockito 5, which requires Java 11 as the minimum version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11324) NAR Plugin extension docs not correctly resolving overridden versions from system properties
[ https://issues.apache.org/jira/browse/NIFI-11324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-11324: --- Fix Version/s: (was: nifi-nar-maven-plugin-1.5.1) > NAR Plugin extension docs not correctly resolving overridden versions from > system properties > > > Key: NIFI-11324 > URL: https://issues.apache.org/jira/browse/NIFI-11324 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: nifi-nar-maven-plugin-1.3.4, > nifi-nar-maven-plugin-1.4.0, nifi-nar-maven-plugin-1.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > In a NAR project with a property like 1.19.1 > defined, it seems that if you build the NAR and specify > -Dnifi.version=1.20.0, it still shows trying to resolve 1.19.1 artifacts > during generation of the extension documentation, even though the final NAR > correctly has the 1.20.0 jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11324) NAR Plugin extension docs not correctly resolving overridden versions from system properties
[ https://issues.apache.org/jira/browse/NIFI-11324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-11324: --- Status: Patch Available (was: Open) > NAR Plugin extension docs not correctly resolving overridden versions from > system properties > > > Key: NIFI-11324 > URL: https://issues.apache.org/jira/browse/NIFI-11324 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: nifi-nar-maven-plugin-1.5.0, > nifi-nar-maven-plugin-1.4.0, nifi-nar-maven-plugin-1.3.4 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > In a NAR project with a property like 1.19.1 > defined, it seems that if you build the NAR and specify > -Dnifi.version=1.20.0, it still shows trying to resolve 1.19.1 artifacts > during generation of the extension documentation, even though the final NAR > correctly has the 1.20.0 jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi-maven] bbende opened a new pull request, #33: NIFI-11324 Set system properties in the user properties of artifact r…
bbende opened a new pull request, #33: URL: https://github.com/apache/nifi-maven/pull/33 …equests -- 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
[GitHub] [nifi] markobean commented on pull request #7057: NIFI-11302: add Registry version to About dialog fixing bug for Java 11
markobean commented on PR #7057: URL: https://github.com/apache/nifi/pull/7057#issuecomment-1479757996 Accepted recommendation to modify and use the manifest to obtain information. Pushed changes. Thanks @exceptionfactory for the 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
[jira] [Created] (NIFI-11324) NAR Plugin extension docs not correctly resolving overridden versions from system properties
Bryan Bende created NIFI-11324: -- Summary: NAR Plugin extension docs not correctly resolving overridden versions from system properties Key: NIFI-11324 URL: https://issues.apache.org/jira/browse/NIFI-11324 Project: Apache NiFi Issue Type: Bug Affects Versions: nifi-nar-maven-plugin-1.5.0, nifi-nar-maven-plugin-1.4.0, nifi-nar-maven-plugin-1.3.4 Reporter: Bryan Bende Assignee: Bryan Bende Fix For: nifi-nar-maven-plugin-1.5.1 In a NAR project with a property like 1.19.1 defined, it seems that if you build the NAR and specify -Dnifi.version=1.20.0, it still shows trying to resolve 1.19.1 artifacts during generation of the extension documentation, even though the final NAR correctly has the 1.20.0 jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11312) NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
[
https://issues.apache.org/jira/browse/NIFI-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-11312:
Fix Version/s: 2.0.0
1.21.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
> --
>
> Key: NIFI-11312
> URL: https://issues.apache.org/jira/browse/NIFI-11312
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0, 1.21.0, 1.latest, 2.latest
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{dockermaven}} and {{dockerhub}} image builds are not consistent, e.g.
> then have different startup scripts copied into the images (some of which
> contain issues like incorrect properties being used).
> See https://github.com/apache/nifi/pull/6995 (for NIFI-7060) for a more
> complete list of known inconsistences that should be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11312) NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
[
https://issues.apache.org/jira/browse/NIFI-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703693#comment-17703693
]
ASF subversion and git services commented on NIFI-11312:
Commit 110912fcfbba7c7f9147a860ebfdbaa05daa99f5 in nifi's branch
refs/heads/support/nifi-1.x from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=110912fcfb ]
NIFI-11312 Rationalised Registry Docker scripts in one location
This closes #7064
Signed-off-by: David Handermann
> NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
> --
>
> Key: NIFI-11312
> URL: https://issues.apache.org/jira/browse/NIFI-11312
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{dockermaven}} and {{dockerhub}} image builds are not consistent, e.g.
> then have different startup scripts copied into the images (some of which
> contain issues like incorrect properties being used).
> See https://github.com/apache/nifi/pull/6995 (for NIFI-7060) for a more
> complete list of known inconsistences that should be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11312) NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
[
https://issues.apache.org/jira/browse/NIFI-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703692#comment-17703692
]
ASF subversion and git services commented on NIFI-11312:
Commit c7df46eefde41931235f2f6af62ff381eed7ae25 in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c7df46eefd ]
NIFI-11312 Rationalised Registry Docker scripts in one location
This closes #7064
Signed-off-by: David Handermann
> NiFi Registry Docker Image builds are inconsistent (dockermaven vs. dockerhub)
> --
>
> Key: NIFI-11312
> URL: https://issues.apache.org/jira/browse/NIFI-11312
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{dockermaven}} and {{dockerhub}} image builds are not consistent, e.g.
> then have different startup scripts copied into the images (some of which
> contain issues like incorrect properties being used).
> See https://github.com/apache/nifi/pull/6995 (for NIFI-7060) for a more
> complete list of known inconsistences that should be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #7064: NIFI-11312 rationalise nifi-registry docker image startup scripts
exceptionfactory closed pull request #7064: NIFI-11312 rationalise nifi-registry docker image startup scripts URL: https://github.com/apache/nifi/pull/7064 -- 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
[GitHub] [nifi] mark-bathori commented on pull request #6985: NIFI-11215: Add custom validation for KerberosUserService in PutIceberg
mark-bathori commented on PR #6985: URL: https://github.com/apache/nifi/pull/6985#issuecomment-1479650267 Thanks @Lehel44 and @turcsanyip for the reviews. I've updated my PR with unit tests for the custom validation. -- 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
[GitHub] [nifi] markap14 commented on pull request #7003: NIFI-11241: Initial implementation of Python-based Processor API with…
markap14 commented on PR #7003: URL: https://github.com/apache/nifi/pull/7003#issuecomment-1479640307 Pushed a commit that I think addresses all of your mentioned concerns thus far @exceptionfactory and rebased against main in order to resolve conflict in StandardProcessScheduler. Force-pushed due to the rebase. -- 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-11305) CaptureChangeMySQL does not stop if the queue is not empty
[ https://issues.apache.org/jira/browse/NIFI-11305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-11305. --- Resolution: Fixed > CaptureChangeMySQL does not stop if the queue is not empty > -- > > Key: NIFI-11305 > URL: https://issues.apache.org/jira/browse/NIFI-11305 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 1h > Remaining Estimate: 0h > > There is a logic bug in the handling of stopping the CaptureChangeMySQL > processor. This causes it to not stop while there are events in the queue. If > the processor isn't running fast enough to drain the queue, stopping the > processor will have no effect. > The logic was being handled in OnStopped, but that won't get called until the > onTrigger has finished. Instead the loop should be checking to see if the > processor is still scheduled using isScheduled(), and if not should break out > of the loop and finish the onTrigger processing, thereby allowing the > OnStopped logic to be executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11305) CaptureChangeMySQL does not stop if the queue is not empty
[ https://issues.apache.org/jira/browse/NIFI-11305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703675#comment-17703675 ] ASF subversion and git services commented on NIFI-11305: Commit 3321de01f210aaadf9f6a3c9628b8e99a6fa72cf in nifi's branch refs/heads/support/nifi-1.x from Matt Burgess [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3321de01f2 ] NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL (#7068) NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL - Changed to allow 'unexpected' events to still be processed > CaptureChangeMySQL does not stop if the queue is not empty > -- > > Key: NIFI-11305 > URL: https://issues.apache.org/jira/browse/NIFI-11305 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 50m > Remaining Estimate: 0h > > There is a logic bug in the handling of stopping the CaptureChangeMySQL > processor. This causes it to not stop while there are events in the queue. If > the processor isn't running fast enough to drain the queue, stopping the > processor will have no effect. > The logic was being handled in OnStopped, but that won't get called until the > onTrigger has finished. Instead the loop should be checking to see if the > processor is still scheduled using isScheduled(), and if not should break out > of the loop and finish the onTrigger processing, thereby allowing the > OnStopped logic to be executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] markap14 commented on pull request #7068: NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL
markap14 commented on PR #7068: URL: https://github.com/apache/nifi/pull/7068#issuecomment-1479600605 Thanks @mattyb149 changes look good. +1 merged to main and support branches. -- 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-11305) CaptureChangeMySQL does not stop if the queue is not empty
[ https://issues.apache.org/jira/browse/NIFI-11305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703674#comment-17703674 ] ASF subversion and git services commented on NIFI-11305: Commit 3bf1195f4b71bda845ff02cc58e3ddc15ed48d92 in nifi's branch refs/heads/main from Matt Burgess [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3bf1195f4b ] NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL (#7068) NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL - Changed to allow 'unexpected' events to still be processed > CaptureChangeMySQL does not stop if the queue is not empty > -- > > Key: NIFI-11305 > URL: https://issues.apache.org/jira/browse/NIFI-11305 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0, 1.21.0 > > Time Spent: 50m > Remaining Estimate: 0h > > There is a logic bug in the handling of stopping the CaptureChangeMySQL > processor. This causes it to not stop while there are events in the queue. If > the processor isn't running fast enough to drain the queue, stopping the > processor will have no effect. > The logic was being handled in OnStopped, but that won't get called until the > onTrigger has finished. Instead the loop should be checking to see if the > processor is still scheduled using isScheduled(), and if not should break out > of the loop and finish the onTrigger processing, thereby allowing the > OnStopped logic to be executed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] markap14 merged pull request #7068: NIFI-11305: Fixed out-of-order handling of binlog client shutdown in CaptureChangeMySQL
markap14 merged PR #7068: URL: https://github.com/apache/nifi/pull/7068 -- 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] (MINIFICPP-2074) fix config validators
[ https://issues.apache.org/jira/browse/MINIFICPP-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-2074: --- Description: We are sending UNSIGNED_INT_VALIDATOR for nifi_c2_agent_heartbeat_period on C2 but we are actually parsing it as a time period. (and accepting integers as well (implicetly converted for ms) It should be more consistent than this... > fix config validators > - > > Key: MINIFICPP-2074 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2074 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Marton Szasz >Assignee: Martin Zink >Priority: Major > > We are sending UNSIGNED_INT_VALIDATOR for nifi_c2_agent_heartbeat_period on > C2 but we are actually parsing it as a time period. (and accepting integers > as well (implicetly converted for ms) > It should be more consistent than this... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11323) DBCPConnectionPool does not accept http protocol in driver location
[
https://issues.apache.org/jira/browse/NIFI-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703661#comment-17703661
]
ASF subversion and git services commented on NIFI-11323:
Commit 00707f684fd2f5a6989e520d518811dbfafc26fc in nifi's branch
refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=00707f684f ]
NIFI-11323: Fixed last modified change detection of
dynamicallyModifiesClasspath resources (#7069)
> DBCPConnectionPool does not accept http protocol in driver location
> ---
>
> Key: NIFI-11323
> URL: https://issues.apache.org/jira/browse/NIFI-11323
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Before NIFI-8429 it was possible to provide an HTTP URL for {{Database Driver
> Location(s)}} property on {{DBCPConnectionPool}}.
> NIFI-8429 introduced {{dynamicallyModifiesClasspath(true)}} for the property
> and it seems it does not handle http:// urls properly.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11323) DBCPConnectionPool does not accept http protocol in driver location
[
https://issues.apache.org/jira/browse/NIFI-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-11323:
--
Fix Version/s: 2.0.0
1.21.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> DBCPConnectionPool does not accept http protocol in driver location
> ---
>
> Key: NIFI-11323
> URL: https://issues.apache.org/jira/browse/NIFI-11323
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 2.0.0, 1.21.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Before NIFI-8429 it was possible to provide an HTTP URL for {{Database Driver
> Location(s)}} property on {{DBCPConnectionPool}}.
> NIFI-8429 introduced {{dynamicallyModifiesClasspath(true)}} for the property
> and it seems it does not handle http:// urls properly.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11323) DBCPConnectionPool does not accept http protocol in driver location
[
https://issues.apache.org/jira/browse/NIFI-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703662#comment-17703662
]
ASF subversion and git services commented on NIFI-11323:
Commit 22c072e619e12725fae74c86570392035d5e418f in nifi's branch
refs/heads/support/nifi-1.x from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=22c072e619 ]
NIFI-11323: Fixed last modified change detection of
dynamicallyModifiesClasspath resources (#7069)
> DBCPConnectionPool does not accept http protocol in driver location
> ---
>
> Key: NIFI-11323
> URL: https://issues.apache.org/jira/browse/NIFI-11323
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Before NIFI-8429 it was possible to provide an HTTP URL for {{Database Driver
> Location(s)}} property on {{DBCPConnectionPool}}.
> NIFI-8429 introduced {{dynamicallyModifiesClasspath(true)}} for the property
> and it seems it does not handle http:// urls properly.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] markap14 merged pull request #7069: NIFI-11323: Fixed last modified change detection of dynamicallyModifi…
markap14 merged PR #7069: URL: https://github.com/apache/nifi/pull/7069 -- 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
[GitHub] [nifi] markap14 commented on pull request #7069: NIFI-11323: Fixed last modified change detection of dynamicallyModifi…
markap14 commented on PR #7069: URL: https://github.com/apache/nifi/pull/7069#issuecomment-1479550465 Thanks @turcsanyip this looks like a reasonable change and eliminates a rather specific assumption that won't always be true. +1 will merge. -- 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
[GitHub] [nifi] nandorsoma commented on a diff in pull request #6769: NIFI-10955 - Added JASN1Reader the ability to try to adjust for unsupported ASN features
nandorsoma commented on code in PR #6769:
URL: https://github.com/apache/nifi/pull/6769#discussion_r1144675192
##
nifi-nar-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/java/org/apache/nifi/jasn1/JASN1Reader.java:
##
@@ -193,10 +219,23 @@ protected Collection
customValidate(ValidationContext validati
@OnEnabled
public void onEnabled(final ConfigurationContext context) throws
InitializationException {
if (context.getProperty(ASN_FILES) != null &&
context.getProperty(ASN_FILES).isSet()) {
-String[] asnFilesPaths =
Arrays.stream(context.getProperty(ASN_FILES).evaluateAttributeExpressions().getValue().split(","))
-.map(String::trim)
-.toArray(String[]::new);
+String asnFilesString =
context.getProperty(ASN_FILES).evaluateAttributeExpressions().getValue();
+if (context.getProperty(DO_ADDITIONAL_PREPROCESSING).asBoolean()) {
+AsnPreprocessorEngine asnPreprocessorEngine = new
AsnPreprocessorEngine();
Review Comment:
final is missing
##
nifi-nar-bundles/nifi-asn1-bundle/nifi-asn1-services/src/main/java/org/apache/nifi/jasn1/JASN1Reader.java:
##
@@ -193,10 +219,23 @@ protected Collection
customValidate(ValidationContext validati
@OnEnabled
public void onEnabled(final ConfigurationContext context) throws
InitializationException {
if (context.getProperty(ASN_FILES) != null &&
context.getProperty(ASN_FILES).isSet()) {
-String[] asnFilesPaths =
Arrays.stream(context.getProperty(ASN_FILES).evaluateAttributeExpressions().getValue().split(","))
-.map(String::trim)
-.toArray(String[]::new);
+String asnFilesString =
context.getProperty(ASN_FILES).evaluateAttributeExpressions().getValue();
+if (context.getProperty(DO_ADDITIONAL_PREPROCESSING).asBoolean()) {
+AsnPreprocessorEngine asnPreprocessorEngine = new
AsnPreprocessorEngine();
+
+String preprocessOutputDirectory =
context.getProperty(ADDITIONAL_PREPROCESSING_OUTPUT_DIRECTORY).evaluateAttributeExpressions().getValue();
Review Comment:
final is missing. Also in line 236, but I cannot comment on it.
##
nifi-nar-bundles/nifi-asn1-bundle/nifi-asn1-services/src/test/resources/preprocessed_test_complex_for_preprocessing.asn:
##
@@ -0,0 +1,15 @@
+ORG-APACHE-NIFI-JASN1-TEST
+
+DEFINITIONS IMPLICIT TAGS ::=
+
+BEGIN
+
+MyType := SEQUENCE {
Review Comment:
An additional colon is missing.
```suggestion
MyType ::= SEQUENCE {
```
##
nifi-nar-bundles/nifi-asn1-bundle/nifi-asn1-services/src/test/resources/test_complex_for_preprocessing.asn:
##
@@ -0,0 +1,15 @@
+ORG-APACHE-NIFI-JASN1-TEST
+
+DEFINITIONS IMPLICIT TAGS ::=
+
+BEGIN
+
+MyType := SEQUENCE {
Review Comment:
An additional colon is missing.
```suggestion
MyType ::= SEQUENCE {
```
--
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-9890) Record conversion fails in JoltTransformREcord
[
https://issues.apache.org/jira/browse/NIFI-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Hynar resolved NIFI-9890.
Fix Version/s: 1.20.0
Resolution: Fixed
The problem is eventually fixed in 1.20.0
> Record conversion fails in JoltTransformREcord
> --
>
> Key: NIFI-9890
> URL: https://issues.apache.org/jira/browse/NIFI-9890
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.3
>Reporter: Martin Hynar
>Priority: Major
> Fix For: 1.20.0
>
>
> Hello, I am struggling with JOLT transformation of record flow file. The flow
> is quite simple
> # Consume records from Kafka - ConsumeKafkaRecord, where reader is Avro
> Reader Confluent Reference and writer is Json Record Set - this step is OK
> and flowfiles are correctly sent to success.
> # Transform records - using JoltTransformRecord, with JsonTreeReader and
> Json Record Set Writer - the transformation is very simple, new field is
> created from existing fields. On writing result, bellow exception is thrown.
> Worth mentioning, the problematic field is not used in the transformation at
> all.
> The exception is this
>
> {code:java}
> 2022-04-07 03:32:40,170 ERROR [Timer-Driven Process Thread-1]
> o.a.n.p.jolt.record.JoltTransformRecord
> JoltTransformRecord[id=2ea633ad-c1f3-1909--686dd600] Unable to
> transform
> StandardFlowFileRecord[uuid=e32039eb-e7f9-46ea-a7a4-ad9cf3709b71,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1649063785609-18280,
> container=default, section=872], offset=381094,
> length=1143917],offset=0,name=e32039eb-e7f9-46ea-a7a4-ad9cf3709b71,size=1143917]
> due to
> org.apache.nifi.serialization.record.util.IllegalTypeConversionException:
> Cannot convert value [[Ljava.lang.Object;@d786ea4] of type
> CHOICE[ARRAY[STRING], ARRAY[INT]] to Map for field IgnoreIssues because the
> type is not supported:
> org.apache.nifi.serialization.record.util.IllegalTypeConversionException:
> Cannot convert value [[Ljava.lang.Object;@d786ea4] of type
> CHOICE[ARRAY[STRING], ARRAY[INT]] to Map for field IgnoreIssues because the
> type is not supported
> org.apache.nifi.serialization.record.util.IllegalTypeConversionException:
> Cannot convert value [[Ljava.lang.Object;@d786ea4] of type
> CHOICE[ARRAY[STRING], ARRAY[INT]] to Map for field IgnoreIssues because the
> type is not supported
> at
> org.apache.nifi.serialization.record.util.DataTypeUtils.convertRecordFieldtoObject(DataTypeUtils.java:858)
> at
> org.apache.nifi.processors.jolt.record.JoltTransformRecord.transform(JoltTransformRecord.java:409)
> at
> org.apache.nifi.processors.jolt.record.JoltTransformRecord.onTrigger(JoltTransformRecord.java:334)
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1273)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834) {code}
>
> What I found about the field is that in the record, there are these values
> {noformat}
> "IgnoreIssues" : [ ],
> "IgnoreIssues" : [ ],
> "IgnoreIssues" : [ 0 ],
> "IgnoreIssues" : [ 0 ],
> "IgnoreIssues" : [ ],
> "IgnoreIssues" : [ ],
> {noformat}
> so, single value arrays mixed with empty arrays.
>
> Also, what I tried was to redirect all failed flow files into SplitRecord
> processor with max records = 1. When these single record flowfiles were
> returned to the same transformation, they passed.
> The array is very often empty and I have flow files that pass the
> transformation, I think it is when all records have empty array in this field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MINIFICPP-2083) CronTests fails on ARM64
Martin Zink created MINIFICPP-2083:
--
Summary: CronTests fails on ARM64
Key: MINIFICPP-2083
URL: https://issues.apache.org/jira/browse/MINIFICPP-2083
Project: Apache NiFi MiNiFi C++
Issue Type: Bug
Reporter: Martin Zink
{code:java}
---
Cron expression ctor tests
---
/nifi-minifi-cpp/libminifi/test/unit/CronTests.cpp:35
...
/nifi-minifi-cpp/libminifi/test/unit/CronTests.cpp:104: FAILED:
REQUIRE_NOTHROW( Cron("0 10,44 14 ? 3 WED") )
due to unexpected exception with message:
Couldn't parse cron field: WED Invalid weekday: WED
---
Cron allowed nonnumerical inputs
---
/nifi-minifi-cpp/libminifi/test/unit/CronTests.cpp:125
...
/nifi-minifi-cpp/libminifi/test/unit/CronTests.cpp:126: FAILED:
REQUIRE_NOTHROW( Cron("* * * *
Jan,fEb,MAR,Apr,May,jun,Jul,Aug,Sep,Oct,Nov,Dec * *") )
due to unexpected exception with message:
Couldn't parse cron field: Jan,fEb,MAR,Apr,May,jun,Jul,Aug,Sep,Oct,Nov,Dec
Invalid month fEb
===
test cases: 4 | 2 passed | 2 failed
assertions: 598 | 596 passed | 2 failed {code}
Encountered on RockyLinux:9 aarch64
{code:java}
Linux 4a12e7385b51 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022
aarch64 aarch64 aarch64 GNU/Linux {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11320) Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2
[ https://issues.apache.org/jira/browse/NIFI-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-11320: -- Fix Version/s: 2.0.0 1.21.0 (was: 1.latest) (was: 2.latest) Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2 > --- > > Key: NIFI-11320 > URL: https://issues.apache.org/jira/browse/NIFI-11320 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 2.0.0, 1.21.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded to > [5.3.26|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.26] > and Spring Security should be upgraded to > [5.8.2|https://github.com/spring-projects/spring-security/releases/tag/5.8.2] > to incorporate minor bug fixes and improvements over the current versions. > Spring Boot for NiFi Registry should be upgraded to > [2.7.9|https://github.com/spring-projects/spring-boot/releases/tag/v2.7.9]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11320) Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2
[ https://issues.apache.org/jira/browse/NIFI-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703575#comment-17703575 ] ASF subversion and git services commented on NIFI-11320: Commit 771d2897799e39880113cb1617626de613af5a87 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=771d289779 ] NIFI-11320 Upgraded Spring Framework from 5.3.24 to 5.3.26 - Upgraded Spring Security from 5.8.0 to 5.8.2 - Upgraded Spring Boot from 2.7.6 to 2.7.9 for NiFi Registry Signed-off-by: Pierre Villard This closes #7067. > Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2 > --- > > Key: NIFI-11320 > URL: https://issues.apache.org/jira/browse/NIFI-11320 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 20m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded to > [5.3.26|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.26] > and Spring Security should be upgraded to > [5.8.2|https://github.com/spring-projects/spring-security/releases/tag/5.8.2] > to incorporate minor bug fixes and improvements over the current versions. > Spring Boot for NiFi Registry should be upgraded to > [2.7.9|https://github.com/spring-projects/spring-boot/releases/tag/v2.7.9]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11320) Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2
[ https://issues.apache.org/jira/browse/NIFI-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703574#comment-17703574 ] ASF subversion and git services commented on NIFI-11320: Commit 69aa181fde577e51e1ffe7d8dbd3be45a8722a01 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=69aa181fde ] NIFI-11320 Upgraded Spring Framework from 5.3.24 to 5.3.26 - Upgraded Spring Security from 5.8.0 to 5.8.2 - Upgraded Spring Boot from 2.7.6 to 2.7.9 for NiFi Registry Signed-off-by: Pierre Villard This closes #7067. > Upgrade Spring Framework to 5.3.26 and Spring Security to 5.8.2 > --- > > Key: NIFI-11320 > URL: https://issues.apache.org/jira/browse/NIFI-11320 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, MiNiFi, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: dependency-upgrade > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded to > [5.3.26|https://github.com/spring-projects/spring-framework/releases/tag/v5.3.26] > and Spring Security should be upgraded to > [5.8.2|https://github.com/spring-projects/spring-security/releases/tag/5.8.2] > to incorporate minor bug fixes and improvements over the current versions. > Spring Boot for NiFi Registry should be upgraded to > [2.7.9|https://github.com/spring-projects/spring-boot/releases/tag/v2.7.9]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] asfgit closed pull request #7067: NIFI-11320 Upgrade Spring Framework from 5.3.24 to 5.3.26
asfgit closed pull request #7067: NIFI-11320 Upgrade Spring Framework from 5.3.24 to 5.3.26 URL: https://github.com/apache/nifi/pull/7067 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MINIFICPP-2082) Move rocksdb metrics from printStats to RepositoryMetrics
Gábor Gyimesi created MINIFICPP-2082: Summary: Move rocksdb metrics from printStats to RepositoryMetrics Key: MINIFICPP-2082 URL: https://issues.apache.org/jira/browse/MINIFICPP-2082 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Gábor Gyimesi Assignee: Gábor Gyimesi The printStats function in rocksdb flowfile and provenance repositories logs some rocksdb statistics to the application logs. These statistics should be moved to the RepositoryMetrics node so it could be published to any metric collector, but also still could be pushed to the application logs after logging metrics is implemented in https://issues.apache.org/jira/browse/MINIFICPP-2076 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINIFICPP-2079) out of memory during python.feature
[ https://issues.apache.org/jira/browse/MINIFICPP-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-2079: --- Resolution: Fixed Status: Resolved (was: Patch Available) https://github.com/apache/nifi-minifi-cpp/commit/333971ad52757b04c543c2808592894f8596716d > out of memory during python.feature > --- > > Key: MINIFICPP-2079 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2079 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario: Native python processors can be stateful sometimes runs out of > memory -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINIFICPP-2075) Fix flaky PutTCPTests testcase
[ https://issues.apache.org/jira/browse/MINIFICPP-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-2075: --- Resolution: Fixed Status: Resolved (was: Patch Available) https://github.com/apache/nifi-minifi-cpp/commit/be34911e89118aaa5071da91b4b9cea71e5cb2da > Fix flaky PutTCPTests testcase > --- > > Key: MINIFICPP-2075 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2075 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] simonbence opened a new pull request, #7070: NIFI-11319 Fixing TestStatelessBootstrap::testClassNotAllowed
simonbence opened a new pull request, #7070: URL: https://github.com/apache/nifi/pull/7070 The test was broken. My understaning is that the test supposed to ensure that classes from outside the allowed NAR directory should not be loaded expect if they are part of a spefic set of classes (java or jdk "modules"). The original configuration of the test used the "target" folder as NAR folder, which contained every product of the build, including the class "org.apache.nifi.stateless.bootstrap.RunStatelessFlow" used as test subject, thus the class was loaded and the test broke. I narrowed down the "nar folder" in order to not have the test subject included, this I would believe solves the issue. [NIFI-11319](https://issues.apache.org/jira/browse/NIFI-11319) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] 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 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
