[jira] [Commented] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[ https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479862#comment-17479862 ] liuke commented on NIFI-9603: - Hello, it has been replaced with PDF file > When a processor group is stopped or started in the UI, the thread pool > cannot execute any tasks > > > Key: NIFI-9603 > URL: https://issues.apache.org/jira/browse/NIFI-9603 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.9.0 > Environment: nifi version:1.9.0 > Server：CentOS Linux release 7.9.2009 > Deployment mode: 5-node cluster > The maximum timer driven thread count is set to 350 > JDK version is "1.8.0_181" >Reporter: liuke >Priority: Major > Attachments: description.pdf, dump.log, nifi-app_2022-01-21_09.34.log > > Original Estimate: 192h > Remaining Estimate: 192h > > See the attachment for the picture > > Problem phenomenon > # This problem is probably triggered when a processor group (including > multiple processors) is stopped in the interface > # Nifi cluster UI “Active Thread Count”becomes 0 > # The task cannot be executed. The UI shows that the thread is stuck > # Analysis using jstack，The stack information is intercepted many times at a > long time interval, and the information is the following results: total > 350 thread, one of which is timed_ Waiting, The remaining 349 are waiting -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] thenatog commented on pull request #5694: NIFI-5402 - Disable the tar.gz build artifact by default. Build will …
thenatog commented on pull request #5694: URL: https://github.com/apache/nifi/pull/5694#issuecomment-1018204238 Updated to build with the -Ptargz profile and added the profile to other assembly poms. -- 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-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Description:
See the attachment for the picture
Problem phenomenon
# This problem is probably triggered when a processor group (including
multiple processors) is stopped in the interface
# Nifi cluster UI “Active Thread Count”becomes 0
# The task cannot be executed. The UI shows that the thread is stuck
# Analysis using jstack，The stack information is intercepted many times at a
long time interval, and the information is the following results: total 350
thread, one of which is timed_ Waiting, The remaining 349 are waiting
was:
See the attachment for the picture
Problem phenomenon
# This problem is probably triggered when a processor group (including
multiple processors) is stopped in the interface
# Nifi cluster interface activethreadcount becomes 0
# The task cannot be executed. The UI shows that the thread is stuck
# Analysis using jstack，{*}The stack information is intercepted many times at
a long time interval,{*} and the information is the following results: total
300 thread, one of which is timed_ Waiting, The remaining 299 are waiting
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.pdf, dump.log, nifi-app_2022-01-21_09.34.log
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster UI “Active Thread Count”becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，The stack information is intercepted many times at a
> long time interval, and the information is the following results: total
> 350 thread, one of which is timed_ Waiting, The remaining 349 are waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Attachment: nifi-app_2022-01-21_09.34.log
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.pdf, dump.log, nifi-app_2022-01-21_09.34.log
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Attachment: dump.log
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.pdf, dump.log, nifi-app_2022-01-21_09.34.log
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Attachment: description.pdf
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.pdf
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Attachment: (was: description.docx)
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9517) "Too many files with unapproved license" occurs when running mvn install
[
https://issues.apache.org/jira/browse/NIFI-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479747#comment-17479747
]
Paul Grey commented on NIFI-9517:
-
Hi [~sunyd1224]. Just noticed this ticket today.
>From time to time, modules are moved in the project to better organize it. I
>think this might be the explanation for your problem. I usually don't run
>"contrib-check" on my development machine, but I tried it today, and ran into
>the same issue.
https://stackoverflow.com/questions/1499157/git-checkout-pull-doesnt-remove-directories
I found this resource that explains how files can be left behind on your
filesystem when they are removed from the git repository. Can you try the
command in the accepted solution, and see if it helps? (I needed the `-x`
switch as well.)
https://github.com/sunyd1224/nifi/actions/runs/1618089119
The automation that runs on your github fork includes the `contrib-check`
switch, so that also works to meet the guideline.
> "Too many files with unapproved license" occurs when running mvn install
>
>
> Key: NIFI-9517
> URL: https://issues.apache.org/jira/browse/NIFI-9517
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Affects Versions: 1.16.0
> Environment: os: windows 10
> java version: 1.8.0_311
> maven version: 3.8.4
>Reporter: sunyd1224
>Priority: Major
> Attachments: .plxarc, createdFiles.lst, inputFiles.lst,
> pom.properties, rat.txt
>
>
> I ran the flowing command to execute the full suite of tests at the root
> nifi folder:
> {code:java}
> mvn -Pcontrib-check clean install {code}
> There was a built failure occurs with the following error message:
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:41 min
> [INFO] Finished at: 2021-12-24T16:20:24+08:00
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check
> (default) on project nifi-framework: Too many files with unapproved license:
> 4 See RAT report in:
> D:\workspace\nifi_github\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\target\rat.txt
> -> [Help 1] {code}
> When I ran "{_}mvn clean install{_}" ,this kind of error disappeard.
> As the "{_}mvn -Pcontrib-check clean install{_}" is required to run when
> create a pr and I could not solve this problem so far, I create this issue to
> ask for help here. The related file are in the attachment.
> Tks.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] joewitt commented on pull request #5694: NIFI-5402 - Disable the tar.gz build artifact by default. Build will …
joewitt commented on pull request #5694: URL: https://github.com/apache/nifi/pull/5694#issuecomment-1017993781 I'd just call it 'targz' to be consistent with teh 'rpm' profile that follows right after. Can we please take care of all assemblies at once? There are a lot of tar.gz/zip pairs as default convenience artifacts so lets just tackle them in one if you dont mind. -- 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] thenatog opened a new pull request #5694: NIFI-5402 - Disable the tar.gz build artifact by default. Build will …
thenatog opened a new pull request #5694:
URL: https://github.com/apache/nifi/pull/5694
…only generate a .zip unless specifying the maven profile -Pbuild-tar-gz
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
_Enables X functionality; fixes bug NIFI-._
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [ ] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [nifi] greyp9 commented on pull request #5690: NIFI-9586 - exclude assemblies from CI
greyp9 commented on pull request #5690: URL: https://github.com/apache/nifi/pull/5690#issuecomment-1017989027 The Windows build succeeded (second try) on the source branch: - https://github.com/greyp9/nifi/actions/runs/172422 ``` https://github.com/greyp9/nifi/runs/4888036073 Filesystem 1K-blocks Used Available Use% Mounted on C:/Program Files/Git 267921404 177191452 90729952 67% / D:14678012 1904188 12773824 13% /d Filesystem 1K-blocks Used Available Use% Mounted on C:/Program Files/Git 267921404 180197800 87723604 68% / D:14678012 11376304 3301708 78% /d ``` looks like ~1.5G is saved -- 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] guimou commented on pull request #5684: NIFI-9605: Docker Images for OpenShift
guimou commented on pull request #5684: URL: https://github.com/apache/nifi/pull/5684#issuecomment-1017977539 Hard-coded versions bumped to 1.16.0 as suggested. -- 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-fds] scottyaslan commented on a change in pull request #60: [NIFI-9554] update node/npm versions and frontend deps
scottyaslan commented on a change in pull request #60:
URL: https://github.com/apache/nifi-fds/pull/60#discussion_r789185984
##
File path: platform/core/snackbars/fds-snackbars.module.js
##
@@ -38,6 +32,10 @@ import {
} from './services/snackbar.service';
import { FdsCoasterComponent } from './coaster/coaster.component';
+import {MatSnackBarModule} from "@angular/material/snack-bar";
Review comment:
ty... not sure why the linter didn't complain...
--
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-9611) Remove unnecessary references to nifi-processor-utils
[
https://issues.apache.org/jira/browse/NIFI-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9611:
---
Status: Patch Available (was: Open)
> Remove unnecessary references to nifi-processor-utils
> -
>
> Key: NIFI-9611
> URL: https://issues.apache.org/jira/browse/NIFI-9611
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A number of extension modules include a dependency on
> {{nifi-processor-utils}}, but do not make use of classes in the module. Most
> of the references appear to be based on {{StandardValidators}}, which is
> provided through {{nifi-utils}}. These modules can be updated to use
> {{nifi-utils}} instead of {{nifi-processor-utils}} to avoid unnecessary
> direct and transitive dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] exceptionfactory opened a new pull request #5693: NIFI-9611 Remove unnecessary references to nifi-processor-utils
exceptionfactory opened a new pull request #5693:
URL: https://github.com/apache/nifi/pull/5693
Description of PR
NIFI-9611 Removes unnecessary references to `nifi-processor-utils` from
multiple modules and adds references to `nifi-utils` where necessary. Several
modules had undeclared dependencies on `commons-lang3` through
`nifi-processor-utils`. Removing and replacing references to
`nifi-processor-utils` removes around 30 MB from the final NiFi binary.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [X] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [X] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (NIFI-9611) Remove unnecessary references to nifi-processor-utils
David Handermann created NIFI-9611:
--
Summary: Remove unnecessary references to nifi-processor-utils
Key: NIFI-9611
URL: https://issues.apache.org/jira/browse/NIFI-9611
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: David Handermann
Assignee: David Handermann
A number of extension modules include a dependency on {{nifi-processor-utils}},
but do not make use of classes in the module. Most of the references appear to
be based on {{StandardValidators}}, which is provided through {{nifi-utils}}.
These modules can be updated to use {{nifi-utils}} instead of
{{nifi-processor-utils}} to avoid unnecessary direct and transitive
dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (NIFI-9612) Remove unnecessary references to nifi-processor-utils
David Handermann created NIFI-9612:
--
Summary: Remove unnecessary references to nifi-processor-utils
Key: NIFI-9612
URL: https://issues.apache.org/jira/browse/NIFI-9612
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: David Handermann
Assignee: David Handermann
A number of extension modules include a dependency on {{nifi-processor-utils}},
but do not make use of classes in the module. Most of the references appear to
be based on {{StandardValidators}}, which is provided through {{nifi-utils}}.
These modules can be updated to use {{nifi-utils}} instead of
{{nifi-processor-utils}} to avoid unnecessary direct and transitive
dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (NIFI-9612) Remove unnecessary references to nifi-processor-utils
[
https://issues.apache.org/jira/browse/NIFI-9612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-9612.
Resolution: Duplicate
> Remove unnecessary references to nifi-processor-utils
> -
>
> Key: NIFI-9612
> URL: https://issues.apache.org/jira/browse/NIFI-9612
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> A number of extension modules include a dependency on
> {{nifi-processor-utils}}, but do not make use of classes in the module. Most
> of the references appear to be based on {{StandardValidators}}, which is
> provided through {{nifi-utils}}. These modules can be updated to use
> {{nifi-utils}} instead of {{nifi-processor-utils}} to avoid unnecessary
> direct and transitive dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi-fds] sardell commented on a change in pull request #60: [NIFI-9554] update node/npm versions and frontend deps
sardell commented on a change in pull request #60:
URL: https://github.com/apache/nifi-fds/pull/60#discussion_r789129527
##
File path: platform/core/snackbars/fds-snackbars.module.js
##
@@ -38,6 +32,10 @@ import {
} from './services/snackbar.service';
import { FdsCoasterComponent } from './coaster/coaster.component';
+import {MatSnackBarModule} from "@angular/material/snack-bar";
Review comment:
This is nit picky, but I think the imports statements should be
formatted like the other existing statements with a space between the curly
brackets and the module name.
--
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-fds] scottyaslan opened a new pull request #60: [NIFI-9554] update node/npm versions and frontend deps
scottyaslan opened a new pull request #60: URL: https://github.com/apache/nifi-fds/pull/60 To test: `npm run clean:install` and verify tests pass. Then `cd target && npm start` and verify the available UX components are available and that the styles match nifi-fds v0.2.0. Thank you for submitting a contribution to Apache NiFi Flow Design System. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with either NIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] Have you written or updated unit tests to verify your changes? - [ ] Have you ensured that a full build and that the full suite of unit tests is executed via npm run clean:install at the root nifi-fds folder? - [ ] Have you written or updated the Apache NiFi Flow Design System demo application to demonstrate any new functionality, provide examples of usage, and to verify your changes via npm start at the nifi-fds/target folder? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-fds? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-fds? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] joewitt commented on pull request #5682: NIFI-9596: Fix newline bug in JythonScriptRunner
joewitt commented on pull request #5682: URL: https://github.com/apache/nifi/pull/5682#issuecomment-1017877632 ok fair enough. thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] mattyb149 commented on pull request #5682: NIFI-9596: Fix newline bug in JythonScriptRunner
mattyb149 commented on pull request #5682: URL: https://github.com/apache/nifi/pull/5682#issuecomment-1017874108 Yes I needed a valid Python statement that wasn't valid on the same line as the first line, and a comment is valid. I can add a comment after the first line to indicate such -- 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] joewitt commented on pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
joewitt commented on pull request #5692: URL: https://github.com/apache/nifi/pull/5692#issuecomment-1017871073 Ahh yeah sorry fair enough. I was really talking about the overall. I totally agree we should minimize duplication as close to zero as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-9610) Refactor nifi-processor-utils to separate modules
David Handermann created NIFI-9610:
--
Summary: Refactor nifi-processor-utils to separate modules
Key: NIFI-9610
URL: https://issues.apache.org/jira/browse/NIFI-9610
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
The {{nifi-processor-utils}} module includes a number of shared classes used in
various components. The module also includes a variety of dependencies that are
not necessary for certain capabilities. These dependencies result in the
inclusion of unnecessary libraries in multiple NAR modules, increasing the size
of the binary distribution. The {{nifi-processor-utils}} module should be
refactored into more discrete modules with limited dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] exceptionfactory commented on pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
exceptionfactory commented on pull request #5692: URL: https://github.com/apache/nifi/pull/5692#issuecomment-1017835872 Thanks for the background @joewitt, that is understandable, although it seems like the same argument could be made for any number of JDBC-based services. The code duplication is a pain point, so I would be more favorable to this change if the implementation inherited from the standard DBCPConnectionPool service. -- 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] joewitt commented on pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
joewitt commented on pull request #5692: URL: https://github.com/apache/nifi/pull/5692#issuecomment-1017832265 I think part of the rub here David is that the existing stuff does work. Requires a bit more user steps/configuration and then folks just assume it is different and don't think it works well with Snowflake. But it does. So this helps ease the user configuration burden and puts up a big flashing sign "hey yep nifi works great for sending data to snowflake". Two birds...one PR. -- 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 commented on pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
exceptionfactory commented on pull request #5692: URL: https://github.com/apache/nifi/pull/5692#issuecomment-1017815068 This PR appears to introduce a large amount of code duplication from the standard DBCPConnectionPool service just to register the Snowflake Driver. Does standard DBCPConnectionPool service not work with the Snowflake Computing JDBC driver? -- 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] joewitt commented on pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
joewitt commented on pull request #5692: URL: https://github.com/apache/nifi/pull/5692#issuecomment-1017811317 It gets long but we might need to call these things 'SnowflakeComputing' since we're referring to a trademarked term and such. -- 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] tpalfy opened a new pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
tpalfy opened a new pull request #5692: URL: https://github.com/apache/nifi/pull/5692 https://issues.apache.org/jira/browse/NIFI-9609 ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with **NIFI-** where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically `main`)? - [ ] Is your initial contribution a single, squashed commit? _Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not `squash` or use `--force` when pushing to allow for clean monitoring of changes._ ### For code changes: - [ ] Have you ensured that the full suite of tests is executed via `mvn -Pcontrib-check clean install` at the root `nifi` folder? - [ ] Have you written or updated unit tests to verify your changes? - [ ] Have you verified that the full build is successful on JDK 8? - [ ] Have you verified that the full build is successful on JDK 11? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the `LICENSE` file, including the main `LICENSE` file under `nifi-assembly`? - [ ] If applicable, have you updated the `NOTICE` file, including the main `NOTICE` file found under `nifi-assembly`? - [ ] If adding new Properties, have you added `.displayName` in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi] Lehel44 opened a new pull request #5691: NIFI-9569: SNMP manager UDP transportmapping changed to 0.0.0.0
Lehel44 opened a new pull request #5691:
URL: https://github.com/apache/nifi/pull/5691
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
https://issues.apache.org/jira/browse/NIFI-9569
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [ ] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [nifi] thenatog commented on a change in pull request #5669: NIFI-9453 - Refactored ListenBeats to use netty.
thenatog commented on a change in pull request #5669:
URL: https://github.com/apache/nifi/pull/5669#discussion_r789037793
##
File path:
nifi-nar-bundles/nifi-beats-bundle/nifi-beats-processors/src/main/java/org/apache/nifi/processors/beats/netty/BeatsFrameDecoder.java
##
@@ -0,0 +1,95 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.beats.netty;
+
+import io.netty.buffer.ByteBuf;
+import io.netty.channel.ChannelHandlerContext;
+import io.netty.handler.codec.ByteToMessageDecoder;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.processor.util.listen.event.EventFactoryUtil;
+import org.apache.nifi.processors.beats.frame.BeatsMetadata;
+import org.apache.nifi.processors.beats.frame.BeatsDecoder;
+import org.apache.nifi.processors.beats.frame.BeatsEncoder;
+import org.apache.nifi.processors.beats.frame.BeatsFrame;
+
+import java.nio.charset.Charset;
+import java.util.List;
+import java.util.Map;
+
+/**
+ * Decode a Beats message's bytes into a BeatsMessage object
+ */
+public class BeatsFrameDecoder extends ByteToMessageDecoder {
+
+private Charset charset;
+private BeatsDecoder decoder;
+private final ComponentLog logger;
+private final BeatsEncoder encoder;
+private final BeatsMessageFactory messageFactory;
+
+public static final byte FRAME_WINDOWSIZE = 0x57, FRAME_DATA = 0x44,
FRAME_COMPRESSED = 0x43, FRAME_ACK = 0x41, FRAME_JSON = 0x4a;
+
+public BeatsFrameDecoder(final ComponentLog logger, final Charset charset)
{
+this.charset = charset;
+this.logger = logger;
+this.encoder = new BeatsEncoder();
+this.messageFactory = new BeatsMessageFactory();
+}
+
+@Override
+protected void decode(final ChannelHandlerContext ctx, final ByteBuf in,
final List out) throws Exception {
+final int total = in.readableBytes();
+final String senderSocket = ctx.channel().remoteAddress().toString();
+this.decoder = new BeatsDecoder(charset, logger);
+
+for (int i = 0; i < total; i++) {
+byte currByte = in.readByte();
+
+// decode the bytes and once we find the end of a frame, handle
the frame
+if (decoder.process(currByte)) {
+
+final List frames = decoder.getFrames();
+
+for (BeatsFrame frame : frames) {
+logger.debug("Received Beats frame with transaction {} and
frame type {}",
+frame.getSeqNumber(), frame.getFrameType());
+// Ignore the WINDOW SIZE type frames as they contain no
payload.
+if (frame.getFrameType() != 0x57) {
+handle(frame, senderSocket, out);
+}
+}
+}
+}
+logger.debug("Done processing buffer");
+}
+
+private void handle(final BeatsFrame frame, final String sender, final
List out) {
+final Map metadata =
EventFactoryUtil.createMapWithSender(sender);
+metadata.put(BeatsMetadata.SEQNUMBER_KEY,
String.valueOf(frame.getSeqNumber()));
+
+/* If frameType is a JSON , parse the frame payload into a JsonElement
so that all JSON elements but "message"
+are inserted into the event metadata.
+
+As per above, the "message" element gets added into the body of the
event
+*/
Review comment:
Yeah I agree I don't quite understand what the comment is trying to
convey given the code. It was a direct copy from the existing BeatsFrameHandler
class. I think I'll remove these comments.
--
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-9606) Remove nifi-security-utils from nifi-framework-api
[
https://issues.apache.org/jira/browse/NIFI-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-9606:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove nifi-security-utils from nifi-framework-api
> --
>
> Key: NIFI-9606
> URL: https://issues.apache.org/jira/browse/NIFI-9606
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{nifi-framework-api}} module includes a dependency on
> {{nifi-security-utils}}, which was introduced as a result of changes in
> NIFI-7680. The {{nifi-framework-api}} module does not have any direct usage
> of components from {{nifi-security-utils}}, and with recent refactoring,
> there should be no need to include this dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9593) Missing catch clauses in Confluent Schema Registry client
[ https://issues.apache.org/jira/browse/NIFI-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479549#comment-17479549 ] ASF subversion and git services commented on NIFI-9593: --- Commit 695c3aabcb920668b5bc89134b1614e8dbc99c76 in nifi's branch refs/heads/main from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=695c3aa ] NIFI-9593 - This closes #5679. Missing catch clauses in Confluent Schema Registry client Signed-off-by: Joe Witt > Missing catch clauses in Confluent Schema Registry client > - > > Key: NIFI-9593 > URL: https://issues.apache.org/jira/browse/NIFI-9593 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Some catch clauses for SchemaNotFoundException are missing and are preventing > the addition of a schema with schema ID but without subject/version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9593) Missing catch clauses in Confluent Schema Registry client
[ https://issues.apache.org/jira/browse/NIFI-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-9593: --- Fix Version/s: 1.16.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Missing catch clauses in Confluent Schema Registry client > - > > Key: NIFI-9593 > URL: https://issues.apache.org/jira/browse/NIFI-9593 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.16.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Some catch clauses for SchemaNotFoundException are missing and are preventing > the addition of a schema with schema ID but without subject/version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9606) Remove nifi-security-utils from nifi-framework-api
[
https://issues.apache.org/jira/browse/NIFI-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479548#comment-17479548
]
ASF subversion and git services commented on NIFI-9606:
---
Commit 0da3994ac890c3cec4d5ca12c1debea2e4016669 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0da3994 ]
NIFI-9606 This closes #5688. Removed nifi-security-utils from nifi-framework-api
Signed-off-by: Joe Witt
> Remove nifi-security-utils from nifi-framework-api
> --
>
> Key: NIFI-9606
> URL: https://issues.apache.org/jira/browse/NIFI-9606
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-framework-api}} module includes a dependency on
> {{nifi-security-utils}}, which was introduced as a result of changes in
> NIFI-7680. The {{nifi-framework-api}} module does not have any direct usage
> of components from {{nifi-security-utils}}, and with recent refactoring,
> there should be no need to include this dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9606) Remove nifi-security-utils from nifi-framework-api
[
https://issues.apache.org/jira/browse/NIFI-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-9606:
---
Fix Version/s: 1.16.0
> Remove nifi-security-utils from nifi-framework-api
> --
>
> Key: NIFI-9606
> URL: https://issues.apache.org/jira/browse/NIFI-9606
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{nifi-framework-api}} module includes a dependency on
> {{nifi-security-utils}}, which was introduced as a result of changes in
> NIFI-7680. The {{nifi-framework-api}} module does not have any direct usage
> of components from {{nifi-security-utils}}, and with recent refactoring,
> there should be no need to include this dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] asfgit closed pull request #5688: NIFI-9606 Remove nifi-security-utils from nifi-framework-api
asfgit closed pull request #5688: URL: https://github.com/apache/nifi/pull/5688 -- 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] asfgit closed pull request #5679: NIFI-9593 - Missing catch clauses in Confluent Schema Registry client
asfgit closed pull request #5679: URL: https://github.com/apache/nifi/pull/5679 -- 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-9609) Create SnowflakeConnectionPool controller service
Tamas Palfy created NIFI-9609: - Summary: Create SnowflakeConnectionPool controller service Key: NIFI-9609 URL: https://issues.apache.org/jira/browse/NIFI-9609 Project: Apache NiFi Issue Type: Improvement Reporter: Tamas Palfy Assignee: Tamas Palfy A Snowflake-specific connection pool controller service would make interacting with Snowflake convenient and user-friendly as well as make NiFi's support for Snowflake more apparent. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] joewitt commented on pull request #5679: NIFI-9593 - Missing catch clauses in Confluent Schema Registry client
joewitt commented on pull request #5679: URL: https://github.com/apache/nifi/pull/5679#issuecomment-1017758638 reviewing -- 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] joewitt commented on pull request #5682: NIFI-9596: Fix newline bug in JythonScriptRunner
joewitt commented on pull request #5682: URL: https://github.com/apache/nifi/pull/5682#issuecomment-1017757809 @mattyb149 Why is it important to remove the header from the test file? Was it critical to verify the scenario under test? If so can we put a comment in that file somewhere indicating this is intentional and/or make it a different test that is so brutally obviously trivial such that a header would be obviously not necessary? -- 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] greyp9 opened a new pull request #5690: NIFI-9586 - exclude assemblies from CI
greyp9 opened a new pull request #5690:
URL: https://github.com/apache/nifi/pull/5690
Description of PR
Recent CI runs have warned of limited available disk space after build
executes.
```
Windows Zulu JDK 8 FR
You are running out of disk space. The runner will stop working when the
machine runs out of disk space. Free space left: 81 MB
```
Address this by excluding additional `*-assembly` modules from the CI build.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [X] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (NIFI-9587) Add JSON output for Prometheus Flow Metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9587: --- Summary: Add JSON output for Prometheus Flow Metrics (was: Add json output for Prometheus metrics) > Add JSON output for Prometheus Flow Metrics > --- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Fix For: 1.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9587: --- Fix Version/s: 1.16.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Fix For: 1.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9587) Add json output for Prometheus metrics
[ https://issues.apache.org/jira/browse/NIFI-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479526#comment-17479526 ] ASF subversion and git services commented on NIFI-9587: --- Commit ccd47de6dca4f9be90bfdbeb193c81e85b953170 in nifi's branch refs/heads/main from Timea Barna [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ccd47de ] NIFI-9587 Added JSON format for Prometheus Flow Metrics This closes #5673 Signed-off-by: David Handermann > Add json output for Prometheus metrics > -- > > Key: NIFI-9587 > URL: https://issues.apache.org/jira/browse/NIFI-9587 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Add json output format endpoint for Prometheus metrics > Add a basic filtering option for the json output -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory closed pull request #5673: NIFI-9587 Add json output for Prometheus metrics
exceptionfactory closed pull request #5673: URL: https://github.com/apache/nifi/pull/5673 -- 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-9604) Apachi NiFi - Error Invoke HTTPS error : certification path to requested target
[ https://issues.apache.org/jira/browse/NIFI-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Gough updated NIFI-9604: --- Priority: Trivial (was: Blocker) > Apachi NiFi - Error Invoke HTTPS error : certification path to requested > target > --- > > Key: NIFI-9604 > URL: https://issues.apache.org/jira/browse/NIFI-9604 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mohan reddy >Priority: Trivial > > I am working on Apache NiFi, where i am trying to invoke HTTPS API and > getting an error > > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9608) Disable automated system-test for Pull Requests
[
https://issues.apache.org/jira/browse/NIFI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9608:
---
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Disable automated system-test for Pull Requests
> ---
>
> Key: NIFI-9608
> URL: https://issues.apache.org/jira/browse/NIFI-9608
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{nifi-system-tests}} have been failing regularly on GitHub automated
> builds due to unresolved issues. The {{system-tests}} workflow should be
> disabled for pull requests until the underlying issues can be corrected for
> automated builds on GitHub.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] exceptionfactory closed pull request #5689: NIFI-9608 Disable system-tests workflow for pull requests
exceptionfactory closed pull request #5689: URL: https://github.com/apache/nifi/pull/5689 -- 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-9608) Disable automated system-test for Pull Requests
[
https://issues.apache.org/jira/browse/NIFI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479501#comment-17479501
]
ASF subversion and git services commented on NIFI-9608:
---
Commit d9873510311fefcb86f7699a31755a621a79f8e5 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d987351 ]
NIFI-9608 Disabled system-tests workflow for pull requests
This closes #5689
Signed-off-by: David Handermann
> Disable automated system-test for Pull Requests
> ---
>
> Key: NIFI-9608
> URL: https://issues.apache.org/jira/browse/NIFI-9608
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{nifi-system-tests}} have been failing regularly on GitHub automated
> builds due to unresolved issues. The {{system-tests}} workflow should be
> disabled for pull requests until the underlying issues can be corrected for
> automated builds on GitHub.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9608) Disable automated system-test for Pull Requests
[
https://issues.apache.org/jira/browse/NIFI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9608:
---
Status: Patch Available (was: Open)
> Disable automated system-test for Pull Requests
> ---
>
> Key: NIFI-9608
> URL: https://issues.apache.org/jira/browse/NIFI-9608
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
>
> The {{nifi-system-tests}} have been failing regularly on GitHub automated
> builds due to unresolved issues. The {{system-tests}} workflow should be
> disabled for pull requests until the underlying issues can be corrected for
> automated builds on GitHub.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] joewitt commented on pull request #5689: NIFI-9608 Disable system-tests workflow for pull requests
joewitt commented on pull request #5689: URL: https://github.com/apache/nifi/pull/5689#issuecomment-1017698338 +1 please 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] exceptionfactory opened a new pull request #5689: NIFI-9608 Disable system-tests workflow for pull requests
exceptionfactory opened a new pull request #5689:
URL: https://github.com/apache/nifi/pull/5689
Description of PR
NIFI-9608 Disables the `system-tests` workflow for pull requests. The
`system-tests` workflow retains the scheduled execution configuration to run
every 24 hours to provide opportunity for additional troubleshooting. Disabling
the `system-tests` workflow for pull requests avoids automated build failures
due to unresolved issues with system tests running on GitHub.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [X] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on JDK 8?
- [ ] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (MINIFICPP-1734) Create a version of the TailFile processor which can be used as a Kubernetes pod for log collection
Ferenc Gerlits created MINIFICPP-1734: - Summary: Create a version of the TailFile processor which can be used as a Kubernetes pod for log collection Key: MINIFICPP-1734 URL: https://issues.apache.org/jira/browse/MINIFICPP-1734 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Ferenc Gerlits Assignee: Ferenc Gerlits Fix For: 0.12.0 Following [~lordgamez]'s design, * create a controller service which can collect the pods (including namespace, pod name, pod uid) and containers available on the current Kubernetes node, and * create a processor which can collect logs from all these containers, subject to regular expression filters. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9608) Disable automated system-test for Pull Requests
David Handermann created NIFI-9608:
--
Summary: Disable automated system-test for Pull Requests
Key: NIFI-9608
URL: https://issues.apache.org/jira/browse/NIFI-9608
Project: Apache NiFi
Issue Type: Improvement
Components: Tools and Build
Reporter: David Handermann
Assignee: David Handermann
The {{nifi-system-tests}} have been failing regularly on GitHub automated
builds due to unresolved issues. The {{system-tests}} workflow should be
disabled for pull requests until the underlying issues can be corrected for
automated builds on GitHub.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (NIFI-9607) PutDatabaseRecord doesn't honor Update Keys when Quote Identifiers is true
Matt Burgess created NIFI-9607: -- Summary: PutDatabaseRecord doesn't honor Update Keys when Quote Identifiers is true Key: NIFI-9607 URL: https://issues.apache.org/jira/browse/NIFI-9607 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Matt Burgess When using the Update Keys property of PutDatabaseTable, if Quote Identifiers is set then invalid SQL (i.e empty WHERE clause) is generated so a failure occurs. This combination should work as expected. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9606) Remove nifi-security-utils from nifi-framework-api
[
https://issues.apache.org/jira/browse/NIFI-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9606:
---
Status: Patch Available (was: Open)
> Remove nifi-security-utils from nifi-framework-api
> --
>
> Key: NIFI-9606
> URL: https://issues.apache.org/jira/browse/NIFI-9606
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-framework-api}} module includes a dependency on
> {{nifi-security-utils}}, which was introduced as a result of changes in
> NIFI-7680. The {{nifi-framework-api}} module does not have any direct usage
> of components from {{nifi-security-utils}}, and with recent refactoring,
> there should be no need to include this dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] exceptionfactory opened a new pull request #5688: NIFI-9606 Remove nifi-security-utils from nifi-framework-api
exceptionfactory opened a new pull request #5688:
URL: https://github.com/apache/nifi/pull/5688
Description of PR
NIFI-9606 Removes `nifi-security-utils` as a dependency in
`nifi-framework-api`. The `nifi-framework-api` module does not include any
direct references to `nifi-security-utils`, and other modules that require
`nifi-security-utils` already include direct dependencies. PR #4436 introduced
`nifi-security-utils` as a dependency in `nifi-framework-api`, but the addition
is no longer necessary.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [X] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [X] Have you verified that the full build is successful on JDK 8?
- [X] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (NIFI-9606) Remove nifi-security-utils from nifi-framework-api
David Handermann created NIFI-9606:
--
Summary: Remove nifi-security-utils from nifi-framework-api
Key: NIFI-9606
URL: https://issues.apache.org/jira/browse/NIFI-9606
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: David Handermann
Assignee: David Handermann
The {{nifi-framework-api}} module includes a dependency on
{{nifi-security-utils}}, which was introduced as a result of changes in
NIFI-7680. The {{nifi-framework-api}} module does not have any direct usage of
components from {{nifi-security-utils}}, and with recent refactoring, there
should be no need to include this dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9604) Apachi NiFi - Error Invoke HTTPS error : certification path to requested target
[ https://issues.apache.org/jira/browse/NIFI-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479484#comment-17479484 ] David Handermann commented on NIFI-9604: [~msingireddy] Thank you reporting this issue. Can you provide some additional details about your configuration? The following details would be helpful for diagnosing the problem: 1. What version of NiFi are you using? 2. What version of Java are you using? 3. What NiFi component are you using, is it InvokeHTTP? 4. Can you provide a full stack trace from the nifi-app.log? > Apachi NiFi - Error Invoke HTTPS error : certification path to requested > target > --- > > Key: NIFI-9604 > URL: https://issues.apache.org/jira/browse/NIFI-9604 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mohan reddy >Priority: Blocker > > I am working on Apache NiFi, where i am trying to invoke HTTPS API and > getting an error > > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi-minifi-cpp] lordgamez opened a new pull request #1245: MINIFICPP-1733 Remove debian buster docker build target
lordgamez opened a new pull request #1245: URL: https://github.com/apache/nifi-minifi-cpp/pull/1245 Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479473#comment-17479473
]
Joe Witt commented on NIFI-9603:
Also the current release is 1.15.3. Can you please attempt to reproduce what
you're seeing on a more recent version such as 1.15.3 and let us know.
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.docx
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1733) Remove unsupported docker build targets
[ https://issues.apache.org/jira/browse/MINIFICPP-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi updated MINIFICPP-1733: - Description: GCC version 11 is not supported on Debian Buster, so building the project with that docker target is currently not possible. Testing on Debian can continue by using the binaries built on the CentOS image. (was: Fedora support was dropped so the fedora docker build target can be removed. GCC version 11 is not supported on Debian Buster, so building the project with that docker target is currently not possible. Testing on Debian can continue by using the binaries built on the CentOS image.) > Remove unsupported docker build targets > --- > > Key: MINIFICPP-1733 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1733 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Gábor Gyimesi >Priority: Minor > > GCC version 11 is not supported on Debian Buster, so building the project > with that docker target is currently not possible. Testing on Debian can > continue by using the binaries built on the CentOS image. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-8006) Additional UI to invoke "Leave group" function
[ https://issues.apache.org/jira/browse/NIFI-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479470#comment-17479470 ] ASF subversion and git services commented on NIFI-8006: --- Commit 3c2793be099fd5cc2ba6682acd379cec18277e2f in nifi's branch refs/heads/main from Adam Kocsis [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3c2793b ] [NIFI-8006] Additional options on UI to leave current process group (#5678) - 'Leave group' action button is added to 'Navigation' - 'Leave group' action works with 'esc' hotkey if no modal, context menu, etc. is open - 'esc' key closes context menu if it is open - user guide is updated with new navigation options This closes #5678 > Additional UI to invoke "Leave group" function > -- > > Key: NIFI-8006 > URL: https://issues.apache.org/jira/browse/NIFI-8006 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.12.1 >Reporter: Svyatoslav >Assignee: Adam Kocsis >Priority: Major > Attachments: image-2020-11-14-21-58-10-635.png > > Time Spent: 4.5h > Remaining Estimate: 0h > > It's not very convenient to open popup-menu and click on the "Leave group" > item to leave the group, especially if a program contains many hierarchically > organized groups. > !image-2020-11-14-21-58-10-635.png! > It would be much easier to move around groups with: > # Toolbar button > # Hot key -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (NIFI-8006) Additional UI to invoke "Leave group" function
[ https://issues.apache.org/jira/browse/NIFI-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-8006. --- Fix Version/s: 1.16.0 Resolution: Fixed > Additional UI to invoke "Leave group" function > -- > > Key: NIFI-8006 > URL: https://issues.apache.org/jira/browse/NIFI-8006 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.12.1 >Reporter: Svyatoslav >Assignee: Adam Kocsis >Priority: Major > Fix For: 1.16.0 > > Attachments: image-2020-11-14-21-58-10-635.png > > Time Spent: 4.5h > Remaining Estimate: 0h > > It's not very convenient to open popup-menu and click on the "Leave group" > item to leave the group, especially if a program contains many hierarchically > organized groups. > !image-2020-11-14-21-58-10-635.png! > It would be much easier to move around groups with: > # Toolbar button > # Hot key -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1733) Remove debian buster docker build target
[ https://issues.apache.org/jira/browse/MINIFICPP-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi updated MINIFICPP-1733: - Summary: Remove debian buster docker build target (was: Remove unsupported docker build targets) > Remove debian buster docker build target > > > Key: MINIFICPP-1733 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1733 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Gábor Gyimesi >Priority: Minor > > GCC version 11 is not supported on Debian Buster, so building the project > with that docker target is currently not possible. Testing on Debian can > continue by using the binaries built on the CentOS image. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] mcgilman merged pull request #5678: NIFI-8006 Additional options on UI to leave current process group
mcgilman merged pull request #5678: URL: https://github.com/apache/nifi/pull/5678 -- 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] guimou commented on pull request #5684: NIFI-9605: Docker Images for OpenShift
guimou commented on pull request #5684: URL: https://github.com/apache/nifi/pull/5684#issuecomment-1017652069 Thanks a lot! I've created the Jira issue and changed the title to point to it. I'll make the changes for 1.16.0, no problem, but are there nightly builds or whatever so that I can test, or do I have to build them myself? -- 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-1733) Remove unsupported docker build targets
Gábor Gyimesi created MINIFICPP-1733: Summary: Remove unsupported docker build targets Key: MINIFICPP-1733 URL: https://issues.apache.org/jira/browse/MINIFICPP-1733 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Gábor Gyimesi Fedora support was dropped so the fedora docker build target can be removed. GCC version 11 is not supported on Debian Buster, so building the project with that docker target is currently not possible. Testing on Debian can continue by using the binaries built on the CentOS image. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9605) Adding container images more compatible with OpenShift
Guillaume Moutier created NIFI-9605: --- Summary: Adding container images more compatible with OpenShift Key: NIFI-9605 URL: https://issues.apache.org/jira/browse/NIFI-9605 Project: Apache NiFi Issue Type: Improvement Reporter: Guillaume Moutier Hi! The Docker images that are currently included are not easy to work with on OpenShift (Red Hat's distibution of Kubernetes, the community version being OKD). Security constraints on OpenShift, like specific uids to run the containers or resticted sets of capabilities, prevent from using these images "as-is". You are forced to introduce security constraints relaxations, grant additional capabilities to standard ServiceAccounts, use initContainers to change files and directories ownership at startup... The goal of this improvement is to include OpenShift-compatible image definitions, so that the different projects or users who want to use NiFi on OpenShift can do it in a simple and secure way. I've already created those images and will submit a PR towards this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1732) Crash in LogCompressorSink
Adam Debreceni created MINIFICPP-1732: - Summary: Crash in LogCompressorSink Key: MINIFICPP-1732 URL: https://issues.apache.org/jira/browse/MINIFICPP-1732 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Adam Debreceni Assignee: Adam Debreceni Nullptr dereference, formatter_ is not protected by a lock. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479429#comment-17479429
]
Joe Witt commented on NIFI-9603:
Hello can you please publish a PDF or set of images instead of a word doc?
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.docx
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi-fds] scottyaslan closed pull request #59: [NIFI-6494] Upgrade to latest LTS release of Node (and npm)
scottyaslan closed pull request #59: URL: https://github.com/apache/nifi-fds/pull/59 -- 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-9603) When a processor group is stopped or started in the UI, the thread pool cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Summary: When a processor group is stopped or started in the UI, the thread
pool cannot execute any tasks (was: When a processor group is stopped or
started in the UI, the thread cannot execute any tasks)
> When a processor group is stopped or started in the UI, the thread pool
> cannot execute any tasks
>
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.docx
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (NIFI-9604) Apachi NiFi - Error Invoke HTTPS error : certification path to requested target
Mohan reddy created NIFI-9604: - Summary: Apachi NiFi - Error Invoke HTTPS error : certification path to requested target Key: NIFI-9604 URL: https://issues.apache.org/jira/browse/NIFI-9604 Project: Apache NiFi Issue Type: Bug Reporter: Mohan reddy I am working on Apache NiFi, where i am trying to invoke HTTPS API and getting an error sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MINIFICPP-1706) Rework script engine management in ExecuteScript processor
[ https://issues.apache.org/jira/browse/MINIFICPP-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi resolved MINIFICPP-1706. -- Fix Version/s: 0.12.0 Resolution: Fixed > Rework script engine management in ExecuteScript processor > -- > > Key: MINIFICPP-1706 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1706 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Gábor Gyimesi >Assignee: Gábor Gyimesi >Priority: Minor > Fix For: 0.12.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In [MINIFICPP-1222|https://issues.apache.org/jira/browse/MINIFICPP-1222] an > issue was raised that the script engines were not handled correctly by > allowing more engines in the queue than the maximum number of concurrent > tasks defined in the ExecutePythonProcessor processor. This issue is also > present in the ExecuteScript processor. > In the ExecutePythonProcessor processor the queue was eventually removed in > https://github.com/apache/nifi-minifi-cpp/pull/1227 due the python's GIL not > allowing real concurrency. In the ExecuteScript processor we should have a > solution that allows concurrency with LUA engines limiting the number of > engines to the maximum concurrent tasks limit, but having a single engine for > Python script executions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory commented on a change in pull request #5687: NIFI-8549 Upgrade MiNiFi sensitive properties algorithm
exceptionfactory commented on a change in pull request #5687: URL: https://github.com/apache/nifi/pull/5687#discussion_r788780229 ## File path: minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md ## @@ -899,7 +897,7 @@ Security Properties: ssl protocol: TLS Sensitive Props: key: -algorithm: PBEWITHMD5AND256BITAES-CBC-OPENSSL +algorithm: NIFI_PBKDF2_AES_GCM_256 provider: BC Review comment: Thanks for catching that, yes, it should be removed. -- 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] Lehel44 commented on pull request #5679: NIFI-9593 - Missing catch clauses in Confluent Schema Registry client
Lehel44 commented on pull request #5679: URL: https://github.com/apache/nifi/pull/5679#issuecomment-101746 Review in progress. -- 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-9600) Remove Elasticsearch 2 Processors
[
https://issues.apache.org/jira/browse/NIFI-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-9600:
--
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove Elasticsearch 2 Processors
> -
>
> Key: NIFI-9600
> URL: https://issues.apache.org/jira/browse/NIFI-9600
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{nifi-elasticsearch-processors}} module includes several processors that
> leverage the Elasticsearch 2.0 library and the deprecated Transport Client.
> These processors should be removed along with the Elasticsearch 2.0 library
> references.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9600) Remove Elasticsearch 2 Processors
[
https://issues.apache.org/jira/browse/NIFI-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479319#comment-17479319
]
ASF subversion and git services commented on NIFI-9600:
---
Commit a4791a55d41cd077d0135f903974ac6d142e7a9e in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a4791a5 ]
NIFI-9600 Removed Elasticsearch 2 Processors
Signed-off-by: Joe Gresock
This closes #5685.
> Remove Elasticsearch 2 Processors
> -
>
> Key: NIFI-9600
> URL: https://issues.apache.org/jira/browse/NIFI-9600
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{nifi-elasticsearch-processors}} module includes several processors that
> leverage the Elasticsearch 2.0 library and the deprecated Transport Client.
> These processors should be removed along with the Elasticsearch 2.0 library
> references.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] asfgit closed pull request #5685: NIFI-9600 Remove Elasticsearch 2 Processors
asfgit closed pull request #5685: URL: https://github.com/apache/nifi/pull/5685 -- 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] gresockj commented on pull request #5685: NIFI-9600 Remove Elasticsearch 2 Processors
gresockj commented on pull request #5685: URL: https://github.com/apache/nifi/pull/5685#issuecomment-1017437187 Sounds good, I'll go ahead and 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] ChrisSamo632 commented on pull request #5685: NIFI-9600 Remove Elasticsearch 2 Processors
ChrisSamo632 commented on pull request #5685: URL: https://github.com/apache/nifi/pull/5685#issuecomment-1017435545 All makes sense to me @gresockj, good to continue tidying up the Elasticsearch processors, thanks @exceptionfactory 👍 -- 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-9603) When a processor group is stopped or started in the UI, the thread cannot execute any tasks
[
https://issues.apache.org/jira/browse/NIFI-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liuke updated NIFI-9603:
Description:
See the attachment for the picture
Problem phenomenon
# This problem is probably triggered when a processor group (including
multiple processors) is stopped in the interface
# Nifi cluster interface activethreadcount becomes 0
# The task cannot be executed. The UI shows that the thread is stuck
# Analysis using jstack，{*}The stack information is intercepted many times at
a long time interval,{*} and the information is the following results: total
300 thread, one of which is timed_ Waiting, The remaining 299 are waiting
was:
See the attachment for the picture
Problem phenomenon
# This problem is probably triggered when a processor group (including
multiple processors) is stopped in the interface
# Nifi cluster interface activethreadcount becomes 0
# The task cannot be executed. The UI shows that the thread is stuck
# Analysis using jstack，{*}The stack information is intercepted many times at
a long time interval,{*} and the information is the following results: total
300 thread, one of which is timed_ Waiting, stack information is，The remaining
299 are waiting and the stack information is
> When a processor group is stopped or started in the UI, the thread cannot
> execute any tasks
> ---
>
> Key: NIFI-9603
> URL: https://issues.apache.org/jira/browse/NIFI-9603
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.9.0
> Environment: nifi version:1.9.0
> Server：CentOS Linux release 7.9.2009
> Deployment mode: 5-node cluster
> The maximum timer driven thread count is set to 350
> JDK version is "1.8.0_181"
>Reporter: liuke
>Priority: Major
> Attachments: description.docx
>
> Original Estimate: 192h
> Remaining Estimate: 192h
>
> See the attachment for the picture
>
> Problem phenomenon
> # This problem is probably triggered when a processor group (including
> multiple processors) is stopped in the interface
> # Nifi cluster interface activethreadcount becomes 0
> # The task cannot be executed. The UI shows that the thread is stuck
> # Analysis using jstack，{*}The stack information is intercepted many times
> at a long time interval,{*} and the information is the following results:
> total 300 thread, one of which is timed_ Waiting, The remaining 299 are
> waiting
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (NIFI-9603) When a processor group is stopped or started in the UI, the thread cannot execute any tasks
liuke created NIFI-9603:
---
Summary: When a processor group is stopped or started in the UI,
the thread cannot execute any tasks
Key: NIFI-9603
URL: https://issues.apache.org/jira/browse/NIFI-9603
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.9.0
Environment: nifi version:1.9.0
Server：CentOS Linux release 7.9.2009
Deployment mode: 5-node cluster
The maximum timer driven thread count is set to 350
JDK version is "1.8.0_181"
Reporter: liuke
Attachments: description.docx
See the attachment for the picture
Problem phenomenon
# This problem is probably triggered when a processor group (including
multiple processors) is stopped in the interface
# Nifi cluster interface activethreadcount becomes 0
# The task cannot be executed. The UI shows that the thread is stuck
# Analysis using jstack，{*}The stack information is intercepted many times at
a long time interval,{*} and the information is the following results: total
300 thread, one of which is timed_ Waiting, stack information is，The remaining
299 are waiting and the stack information is
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (NIFI-9588) Update doc for `nifi.content.repository.archive.max.retention.period`
[ https://issues.apache.org/jira/browse/NIFI-9588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangCheng closed NIFI-9588. > Update doc for `nifi.content.repository.archive.max.retention.period` > - > > Key: NIFI-9588 > URL: https://issues.apache.org/jira/browse/NIFI-9588 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.13.0, 1.12.1, 1.14.0, 1.13.1, 1.13.2, 1.15.0, 1.15.1, > 1.15.2, 1.15.3 >Reporter: ZhangCheng >Assignee: ZhangCheng >Priority: Minor > Fix For: 1.16.0 > > Attachments: image-2022-01-19-14-38-43-385.png, > image-2022-01-19-14-40-50-311.png > > Time Spent: 20m > Remaining Estimate: 0h > > The default value of `nifi.content.repository.archive.max.retention.period` > has been changed to `7 days`. > > > > !image-2022-01-19-14-38-43-385.png|width=813,height=204! > !image-2022-01-19-14-40-50-311.png|width=811,height=211! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] timeabarna commented on pull request #5673: NIFI-9587 Add json output for Prometheus metrics
timeabarna commented on pull request #5673: URL: https://github.com/apache/nifi/pull/5673#issuecomment-1017359679 Thanks @exceptionfactory for the review. -- 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] timeabarna commented on a change in pull request #5673: NIFI-9587 Add json output for Prometheus metrics
timeabarna commented on a change in pull request #5673:
URL: https://github.com/apache/nifi/pull/5673#discussion_r788610509
##
File path:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/test/java/org/apache/nifi/web/api/TestFlowResource.java
##
@@ -174,4 +291,79 @@ private String getResponseOutput(final Response response)
throws IOException {
final CollectorRegistry otherJvmCollectorRegistry =
PrometheusMetricsUtil.createJvmMetrics(jvmMetricsRegistry,
JmxJvmMetrics.getInstance(), OTHER_LABEL_VALUE);
return Arrays.asList(jvmCollectorRegistry, otherJvmCollectorRegistry);
}
+
+private Map>
convertJsonResponseToMap(final Response response) throws IOException {
+final String json = getResponseOutput(response);
+final Type type = new TypeToken>>() {}.getType();
+return new Gson().fromJson(json, type);
Review comment:
As Prometheus Sample has no default constructor and 2 argument
constructors so ObjectMapper was not able to deserialise. I needed to create a
custom deserialiser for Sample.
--
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-1731) Linter targets should not be built by default on Windows
[ https://issues.apache.org/jira/browse/MINIFICPP-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ádám Markovics updated MINIFICPP-1731: -- Description: A run from Jenkins is attached. (was: A run from Jenkins: [^consoleText]) > Linter targets should not be built by default on Windows > > > Key: MINIFICPP-1731 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1731 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Ádám Markovics >Assignee: Ádám Markovics >Priority: Minor > Attachments: consoleText > > > A run from Jenkins is attached. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1731) Linter targets should not be built by default on Windows
[ https://issues.apache.org/jira/browse/MINIFICPP-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ádám Markovics updated MINIFICPP-1731: -- Attachment: consoleText > Linter targets should not be built by default on Windows > > > Key: MINIFICPP-1731 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1731 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Ádám Markovics >Assignee: Ádám Markovics >Priority: Minor > Attachments: consoleText > > > A run from Jenkins: [^consoleText] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1731) Linter targets should not be built by default on Windows
Ádám Markovics created MINIFICPP-1731: - Summary: Linter targets should not be built by default on Windows Key: MINIFICPP-1731 URL: https://issues.apache.org/jira/browse/MINIFICPP-1731 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Ádám Markovics Assignee: Ádám Markovics Attachments: consoleText A run from Jenkins: [^consoleText] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] pvillard31 commented on a change in pull request #5687: NIFI-8549 Upgrade MiNiFi sensitive properties algorithm
pvillard31 commented on a change in pull request #5687: URL: https://github.com/apache/nifi/pull/5687#discussion_r788572625 ## File path: minifi/minifi-docs/src/main/markdown/System_Admin_Guide.md ## @@ -899,7 +897,7 @@ Security Properties: ssl protocol: TLS Sensitive Props: key: -algorithm: PBEWITHMD5AND256BITAES-CBC-OPENSSL +algorithm: NIFI_PBKDF2_AES_GCM_256 provider: BC Review comment: should the provider be removed? -- 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-9599) Review and Update all Explicit Maven Build/Plugin References
[ https://issues.apache.org/jira/browse/NIFI-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-9599: - Component/s: Core Framework Tools and Build > Review and Update all Explicit Maven Build/Plugin References > > > Key: NIFI-9599 > URL: https://issues.apache.org/jira/browse/NIFI-9599 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, Tools and Build >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (NIFI-9599) Review and Update all Explicit Maven Build/Plugin References
[ https://issues.apache.org/jira/browse/NIFI-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard resolved NIFI-9599. -- Fix Version/s: 1.16.0 Resolution: Fixed > Review and Update all Explicit Maven Build/Plugin References > > > Key: NIFI-9599 > URL: https://issues.apache.org/jira/browse/NIFI-9599 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9599) Review and Update all Explicit Maven Build/Plugin References
[ https://issues.apache.org/jira/browse/NIFI-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479216#comment-17479216 ] ASF subversion and git services commented on NIFI-9599: --- Commit fd1c1e354ef933ce16f5e187d0032f18299bd4a9 in nifi's branch refs/heads/main from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fd1c1e3 ] NIFI-9599 updating explicit plugin/build version references Signed-off-by: Pierre Villard This closes #5683. > Review and Update all Explicit Maven Build/Plugin References > > > Key: NIFI-9599 > URL: https://issues.apache.org/jira/browse/NIFI-9599 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] asfgit closed pull request #5683: NIFI-9599 updating explicit plugin/build version references
asfgit closed pull request #5683: URL: https://github.com/apache/nifi/pull/5683 -- 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-9601) Upgrade NiFi Bootstrap to Jakarta Mail 2
[
https://issues.apache.org/jira/browse/NIFI-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-9601:
-
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade NiFi Bootstrap to Jakarta Mail 2
>
>
> Key: NIFI-9601
> URL: https://issues.apache.org/jira/browse/NIFI-9601
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{nifi-bootstrap}} module depends on javax.mail 1.4.7 to support email
> notifications of bootstrap events. The javax.mail 1.4.7 dependency does not
> support recent versions of the TLS protocol, and Jakarta Mail 2 supersedes
> the javax.mail dependency. This dependency and associated references should
> be updated following the same approach as recent updates for the PutEmail
> processor
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9601) Upgrade NiFi Bootstrap to Jakarta Mail 2
[
https://issues.apache.org/jira/browse/NIFI-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479215#comment-17479215
]
ASF subversion and git services commented on NIFI-9601:
---
Commit c42cc61f71478e6d80434787b11521c5c12c8c18 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c42cc61 ]
NIFI-9601 Upgraded nifi-bootstrap to Jakarta Mail 2
Signed-off-by: Pierre Villard
This closes #5686.
> Upgrade NiFi Bootstrap to Jakarta Mail 2
>
>
> Key: NIFI-9601
> URL: https://issues.apache.org/jira/browse/NIFI-9601
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{nifi-bootstrap}} module depends on javax.mail 1.4.7 to support email
> notifications of bootstrap events. The javax.mail 1.4.7 dependency does not
> support recent versions of the TLS protocol, and Jakarta Mail 2 supersedes
> the javax.mail dependency. This dependency and associated references should
> be updated following the same approach as recent updates for the PutEmail
> processor
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] asfgit closed pull request #5686: NIFI-9601 Upgrade nifi-bootstrap to Jakarta Mail 2
asfgit closed pull request #5686: URL: https://github.com/apache/nifi/pull/5686 -- 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] pvillard31 commented on pull request #5686: NIFI-9601 Upgrade nifi-bootstrap to Jakarta Mail 2
pvillard31 commented on pull request #5686: URL: https://github.com/apache/nifi/pull/5686#issuecomment-1017277446 +1, thanks @exceptionfactory -- 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
