[jira] [Commented] (NIFI-9634) Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3
[ https://issues.apache.org/jira/browse/NIFI-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483510#comment-17483510 ] ASF subversion and git services commented on NIFI-9634: --- Commit c8fe5149a5ca3afcb955cd4d572d1081595b564d in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c8fe514 ] NIFI-9634 Upgraded Spring Framework to 5.3.15 - Upgraded Spring Framework from 5.3.14 to 5.3.15 - Upgraded Spring Boot from 2.5.8 to 2.6.3 in Registry - Upgraded Jersey from 2.33 to 2.35 - Upgraded Jackson from 2.12.5 to 2.13.1 Signed-off-by: Nathan Gough This closes #5723. > Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3 > > > Key: NIFI-9634 > URL: https://issues.apache.org/jira/browse/NIFI-9634 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Affects Versions: 1.16.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 1.16.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > NiFi components should be upgraded from Spring Framework 5.3.14 to 5.3.15 and > NiFi Registry should be upgraded from Spring Boot 2.5.8 to 2.6.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9634) Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3
[ https://issues.apache.org/jira/browse/NIFI-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Gough updated NIFI-9634: --- Fix Version/s: 1.16.0 > Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3 > > > Key: NIFI-9634 > URL: https://issues.apache.org/jira/browse/NIFI-9634 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Affects Versions: 1.16.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 1.16.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > NiFi components should be upgraded from Spring Framework 5.3.14 to 5.3.15 and > NiFi Registry should be upgraded from Spring Boot 2.5.8 to 2.6.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9634) Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3
[ https://issues.apache.org/jira/browse/NIFI-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Gough updated NIFI-9634: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3 > > > Key: NIFI-9634 > URL: https://issues.apache.org/jira/browse/NIFI-9634 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Affects Versions: 1.16.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > NiFi components should be upgraded from Spring Framework 5.3.14 to 5.3.15 and > NiFi Registry should be upgraded from Spring Boot 2.5.8 to 2.6.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] thenatog closed pull request #5723: NIFI-9634 Upgrade Spring Framework to 5.3.15
thenatog closed pull request #5723: URL: https://github.com/apache/nifi/pull/5723 -- 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 pull request #5723: NIFI-9634 Upgrade Spring Framework to 5.3.15
thenatog commented on pull request #5723: URL: https://github.com/apache/nifi/pull/5723#issuecomment-1023801320 Tested with a secure NiFi cluster running some test flows. +1 will merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-9637) GCP Secret Manager Parameter Provider
Joe Gresock created NIFI-9637: - Summary: GCP Secret Manager Parameter Provider Key: NIFI-9637 URL: https://issues.apache.org/jira/browse/NIFI-9637 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock Assignee: Joe Gresock Once NIFI-9003 is complete, a Parameter Provider backed by GCP Secret Manager could be written. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9636) AWS Secrets Manager Parameter Provider
Joe Gresock created NIFI-9636: - Summary: AWS Secrets Manager Parameter Provider Key: NIFI-9636 URL: https://issues.apache.org/jira/browse/NIFI-9636 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock Assignee: Joe Gresock Once NIFI-9003 is complete, a Parameter Provider backed by AWS Secrets Manager could be written. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9635) Upgrade Netty to 4.1.73
[ https://issues.apache.org/jira/browse/NIFI-9635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9635: --- Affects Version/s: 1.16.0 Status: Patch Available (was: Open) > Upgrade Netty to 4.1.73 > --- > > Key: NIFI-9635 > URL: https://issues.apache.org/jira/browse/NIFI-9635 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.16.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > [Netty 4.1.73|https://netty.io/news/2022/01/12/4-1-73-Final.html] includes > several improvements and bug fixes. Upgrading from 4.1.72 to 4.1.73 impacts > multiple extension components. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory opened a new pull request #5725: NIFI-9635 Upgrade Netty from 4.1.72 to 4.1.73
exceptionfactory opened a new pull request #5725:
URL: https://github.com/apache/nifi/pull/5725
Description of PR
NIFI-9635 Upgrades Netty from 4.1.72 to 4.1.73 across all framework and
extension components.
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
[GitHub] [nifi] mattyb149 opened a new pull request #5724: NIFI-9585: Upgrade H2 to 2.1.210
mattyb149 opened a new pull request #5724:
URL: https://github.com/apache/nifi/pull/5724
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Upgrades NiFi projects to 2.x
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?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] 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?
- [x] 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-6266) FTP processors do not honor Proxy settings
[
https://issues.apache.org/jira/browse/NIFI-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-6266:
---
Fix Version/s: 1.16.0
> FTP processors do not honor Proxy settings
> ---
>
> Key: NIFI-6266
> URL: https://issues.apache.org/jira/browse/NIFI-6266
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.9.2, 1.11.4, 1.15.2
>Reporter: Steven Arnott
>Assignee: David Handermann
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: image-2019-05-06-10-34-04-951.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Trying to use GetFTP to download a file via our company proxy. But the
> processor does not seem to honor the proxy settings in any way.
> The GetFTP issues a connection timeout error:
> {code:java}
> 2019-05-06 10:32:17,065 ERROR [Timer-Driven Process Thread-10]
> o.apache.nifi.processors.standard.GetFTP
> GetFTP[id=7f520fd2-016a-1000-5012-ae01d3493bfa] Unable to fetch listing from
> remote server due to java.net.ConnectException: Connection timed out
> (Connection timed out): java.net.ConnectException: Connection timed out
> (Connection timed out)
> java.net.ConnectException: Connection timed out (Connection timed out)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.commons.net.SocketClient._connect(SocketClient.java:243)
> at org.apache.commons.net.SocketClient.connect(SocketClient.java:181)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getClient(FTPTransfer.java:585)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:228)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:191)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.fetchListing(GetFileTransfer.java:284)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:127)
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:209)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The process is configured thus to hit a netcat process to see if any
> connection is made
> !image-2019-05-06-10-34-04-951.png!
> When I change the target of the FTP to this debug endpoint it does shows it
> connecting to my listener for the FTP server but not to the proxy.
> Running 1.9.2 in a Docker container.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-6266) FTP processors do not honor Proxy settings
[
https://issues.apache.org/jira/browse/NIFI-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Gough updated NIFI-6266:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> FTP processors do not honor Proxy settings
> ---
>
> Key: NIFI-6266
> URL: https://issues.apache.org/jira/browse/NIFI-6266
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.9.2, 1.11.4, 1.15.2
>Reporter: Steven Arnott
>Assignee: David Handermann
>Priority: Major
> Attachments: image-2019-05-06-10-34-04-951.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Trying to use GetFTP to download a file via our company proxy. But the
> processor does not seem to honor the proxy settings in any way.
> The GetFTP issues a connection timeout error:
> {code:java}
> 2019-05-06 10:32:17,065 ERROR [Timer-Driven Process Thread-10]
> o.apache.nifi.processors.standard.GetFTP
> GetFTP[id=7f520fd2-016a-1000-5012-ae01d3493bfa] Unable to fetch listing from
> remote server due to java.net.ConnectException: Connection timed out
> (Connection timed out): java.net.ConnectException: Connection timed out
> (Connection timed out)
> java.net.ConnectException: Connection timed out (Connection timed out)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.commons.net.SocketClient._connect(SocketClient.java:243)
> at org.apache.commons.net.SocketClient.connect(SocketClient.java:181)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getClient(FTPTransfer.java:585)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:228)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:191)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.fetchListing(GetFileTransfer.java:284)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:127)
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:209)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The process is configured thus to hit a netcat process to see if any
> connection is made
> !image-2019-05-06-10-34-04-951.png!
> When I change the target of the FTP to this debug endpoint it does shows it
> connecting to my listener for the FTP server but not to the proxy.
> Running 1.9.2 in a Docker container.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-6266) FTP processors do not honor Proxy settings
[
https://issues.apache.org/jira/browse/NIFI-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483464#comment-17483464
]
ASF subversion and git services commented on NIFI-6266:
---
Commit 95abc35463d43ea9ee62dc041f85dca38579fec2 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=95abc35 ]
NIFI-6266 Corrected proxy FTP connect handling
- Added ProxyFTPClient with connect method supporting unresolved hosts
- Added FTPClientProvider with implementation handling configuration and
connection
- Added support for SOCKS with authentication in FTP components
- Refactored FTPTransfer using FTPClientProvider
Signed-off-by: Nathan Gough
This closes #5655.
> FTP processors do not honor Proxy settings
> ---
>
> Key: NIFI-6266
> URL: https://issues.apache.org/jira/browse/NIFI-6266
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.9.2, 1.11.4, 1.15.2
>Reporter: Steven Arnott
>Assignee: David Handermann
>Priority: Major
> Attachments: image-2019-05-06-10-34-04-951.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Trying to use GetFTP to download a file via our company proxy. But the
> processor does not seem to honor the proxy settings in any way.
> The GetFTP issues a connection timeout error:
> {code:java}
> 2019-05-06 10:32:17,065 ERROR [Timer-Driven Process Thread-10]
> o.apache.nifi.processors.standard.GetFTP
> GetFTP[id=7f520fd2-016a-1000-5012-ae01d3493bfa] Unable to fetch listing from
> remote server due to java.net.ConnectException: Connection timed out
> (Connection timed out): java.net.ConnectException: Connection timed out
> (Connection timed out)
> java.net.ConnectException: Connection timed out (Connection timed out)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.commons.net.SocketClient._connect(SocketClient.java:243)
> at org.apache.commons.net.SocketClient.connect(SocketClient.java:181)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getClient(FTPTransfer.java:585)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:228)
> at
> org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:191)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.fetchListing(GetFileTransfer.java:284)
> at
> org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:127)
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
> at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:209)
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The process is configured thus to hit a netcat process to see if any
> connection is made
> !image-2019-05-06-10-34-04-951.png!
> When I change the target of the FTP to this debug endpoint it does shows it
> connecting to my listener for the FTP server but not to the proxy.
> Running 1.9.2 in a Docker container.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] thenatog closed pull request #5655: NIFI-6266 Correct proxy FTP connect handling
thenatog closed pull request #5655: URL: https://github.com/apache/nifi/pull/5655 -- 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 pull request #5655: NIFI-6266 Correct proxy FTP connect handling
thenatog commented on pull request #5655: URL: https://github.com/apache/nifi/pull/5655#issuecomment-1023701573 Tested out this PR with a squid proxy + FTP processors. Was able to list files and get files successfully via the proxy. +1 will merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-9635) Upgrade Netty to 4.1.73
David Handermann created NIFI-9635: -- Summary: Upgrade Netty to 4.1.73 Key: NIFI-9635 URL: https://issues.apache.org/jira/browse/NIFI-9635 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: David Handermann Assignee: David Handermann [Netty 4.1.73|https://netty.io/news/2022/01/12/4-1-73-Final.html] includes several improvements and bug fixes. Upgrading from 4.1.72 to 4.1.73 impacts multiple extension components. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9634) Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3
[ https://issues.apache.org/jira/browse/NIFI-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9634: --- Affects Version/s: 1.16.0 Status: Patch Available (was: Open) > Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3 > > > Key: NIFI-9634 > URL: https://issues.apache.org/jira/browse/NIFI-9634 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Affects Versions: 1.16.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > NiFi components should be upgraded from Spring Framework 5.3.14 to 5.3.15 and > NiFi Registry should be upgraded from Spring Boot 2.5.8 to 2.6.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory opened a new pull request #5723: NIFI-9634 Upgrade Spring Framework to 5.3.15
exceptionfactory opened a new pull request #5723:
URL: https://github.com/apache/nifi/pull/5723
Description of PR
NIFI-9634 Upgrades Spring Framework dependencies from 5.3.14 to 5.3.15 and
also upgrades the following related dependencies:
- Upgraded Spring Boot from 2.5.8 to 2.6.3 in Registry
- Upgraded Jersey from 2.33 to 2.35
- Upgraded Jackson from 2.12.5 to 2.13.1
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?
- [ ] 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] [Resolved] (NIFI-9632) Remove deprecated ListenLumberjack processor
[ https://issues.apache.org/jira/browse/NIFI-9632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-9632. Fix Version/s: 1.16.0 Assignee: Nathan Gough Resolution: Fixed > Remove deprecated ListenLumberjack processor > > > Key: NIFI-9632 > URL: https://issues.apache.org/jira/browse/NIFI-9632 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Minor > Fix For: 1.16.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Remove the ListenLumberjack processor that is no longer bundled with NiFi > releases and has been deprecated in favor of ListenBeats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9632) Remove deprecated ListenLumberjack processor
[ https://issues.apache.org/jira/browse/NIFI-9632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483425#comment-17483425 ] ASF subversion and git services commented on NIFI-9632: --- Commit 8f2a9f94fece6d700542d70b9970f714ed4753ef in nifi's branch refs/heads/main from Nathan Gough [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8f2a9f9 ] NIFI-9632 - Removed nifi-lumberjack-bundle - Removed several unused socket classes from nifi-processor-utils This closes #5722 Signed-off-by: David Handermann > Remove deprecated ListenLumberjack processor > > > Key: NIFI-9632 > URL: https://issues.apache.org/jira/browse/NIFI-9632 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Nathan Gough >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Remove the ListenLumberjack processor that is no longer bundled with NiFi > releases and has been deprecated in favor of ListenBeats. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory closed pull request #5722: NIFI-9632 - Removed the lumberjack-bundle and some no longer used soc…
exceptionfactory closed pull request #5722: URL: https://github.com/apache/nifi/pull/5722 -- 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-9634) Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3
David Handermann created NIFI-9634: -- Summary: Upgrade to Spring Framework 5.3.15 and Spring Boot 2.6.3 Key: NIFI-9634 URL: https://issues.apache.org/jira/browse/NIFI-9634 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, NiFi Registry Reporter: David Handermann Assignee: David Handermann NiFi components should be upgraded from Spring Framework 5.3.14 to 5.3.15 and NiFi Registry should be upgraded from Spring Boot 2.5.8 to 2.6.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] thenatog opened a new pull request #5722: NIFI-9632 - Removed the lumberjack-bundle and some no longer used soc…
thenatog opened a new pull request #5722:
URL: https://github.com/apache/nifi/pull/5722
…ket channel classes.
NIFI-9632 - Removed the nifi-lumberjack-bundle from pom.xml.
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:
- [ ] 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] kevdoran commented on pull request #5684: NIFI-9605: Docker Images for OpenShift
kevdoran commented on pull request #5684: URL: https://github.com/apache/nifi/pull/5684#issuecomment-1023518720 Thanks @guimou. Given that we want to offer a variety of base images and platform architectures, I think the first step would be restructuring things such that NiFi image is built in two steps: first to prep the base image, and then the nifi-specific bits. Ideally the nifi-bits would be the same regardless of the base image. Once we get a better handle on that, it should be easier to tackle some of the other wish-list items for docker improvements as there will be fewer files to edit and maintain. Keep an eye out on the wiki/dev mailing list/jira/PRs for opportunities to get involved if you are interested and available! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi-minifi-cpp] szaszm commented on a change in pull request #1251: MINIFICPP-1636 - Use std::filesystem instead of boost and platform specific implementations
szaszm commented on a change in pull request #1251: URL: https://github.com/apache/nifi-minifi-cpp/pull/1251#discussion_r793878534 ## File path: libminifi/include/utils/file/FileUtils.h ## @@ -25,14 +25,7 @@ #include #include -#ifdef USE_BOOST -#include -#include -#include -#ifndef WIN32 -#include -#endif -#else +#ifndef USE_BOOST Review comment: We can now remove this check and just assume that it's not defined. We will eventually get rid of all boost code from libminifi. ## File path: docker/DockerVerify.sh ## @@ -44,11 +44,11 @@ echo "Installing test dependencies..." 1>&2 # hint include/library paths if homewbrew is in use if brew list 2> /dev/null | grep openssl > /dev/null 2>&1; then echo "Using homebrew paths for openssl" 1>&2 - LDFLAGS="-L$(brew --prefix openssl)/lib" + LDFLAGS="-L$(brew --prefix openssl@1.1)/lib" export LDFLAGS - CFLAGS="-I$(brew --prefix openssl)/include" + CFLAGS="-I$(brew --prefix openssl@1.1)/include" export CFLAGS - SWIG_FEATURES="-cpperraswarn -includeall -I$(brew --prefix openssl)/include" + SWIG_FEATURES="-cpperraswarn -includeall -I$(brew --prefix openssl@1.1)/include" Review comment: Why is this version pin? Was something not working on mac? -- 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 a change in pull request #5613: NIFI-9330 - Kafka 3.0 support
exceptionfactory commented on a change in pull request #5613: URL: https://github.com/apache/nifi/pull/5613#discussion_r793835048 ## File path: nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-3-0-processors/pom.xml ## @@ -0,0 +1,154 @@ +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd;> + + +org.apache.nifi +nifi-kafka-bundle +1.16.0-SNAPSHOT + +4.0.0 +nifi-kafka-3-0-processors +jar + + +org.apache.nifi +nifi-api + + +org.apache.nifi +nifi-record-serialization-service-api + + +org.apache.nifi +nifi-record + + +org.apache.nifi +nifi-record-sink-api +1.16.0-SNAPSHOT + + +org.apache.nifi +nifi-processor-utils +1.16.0-SNAPSHOT + Review comment: One additional minor recommendation based on recent refactoring of other Kafka bundles, the dependency on `nifi-processor-utils` should not be necessary. ```suggestion ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [nifi-minifi-cpp] rustammendel opened a new pull request #1251: MINIFICPP-1636 - Use std::filesystem instead of boost and platform specific implementations
rustammendel opened a new pull request #1251: URL: https://github.com/apache/nifi-minifi-cpp/pull/1251 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: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFICPP- 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? ### For code changes: - [x] 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
[GitHub] [nifi] exceptionfactory commented on a change in pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
exceptionfactory commented on a change in pull request #5692:
URL: https://github.com/apache/nifi/pull/5692#discussion_r793828599
##
File path:
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java
##
@@ -0,0 +1,314 @@
+/*
+ * 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.snowflake.service;
+
+import net.snowflake.client.jdbc.SnowflakeDriver;
+import org.apache.commons.dbcp2.BasicDataSource;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.DynamicProperties;
+import org.apache.nifi.annotation.behavior.DynamicProperty;
+import org.apache.nifi.annotation.behavior.RequiresInstanceClassLoading;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnDisabled;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.PropertyValue;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.dbcp.DBCPConnectionPool;
+import org.apache.nifi.expression.AttributeExpression;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.InitializationException;
+
+import java.sql.Connection;
+import java.sql.Driver;
+import java.sql.DriverManager;
+import java.sql.SQLException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Implementation of Database Connection Pooling Service for Snowflake.
+ * Apache DBCP is used for connection pooling functionality.
+ */
+@Tags({"snowflake", "dbcp", "jdbc", "database", "connection", "pooling",
"store"})
+@CapabilityDescription("Provides Snowflake Connection Pooling Service.
Connections can be asked from pool and returned after usage.")
+@DynamicProperties({
+@DynamicProperty(name = "JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.VARIABLE_REGISTRY,
+description = "Snowflake JDBC driver property name and value applied
to JDBC connections."),
+@DynamicProperty(name = "SENSITIVE.JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.NONE,
+description = "Snowflake JDBC driver property name prefixed with
'SENSITIVE.' handled as a sensitive property.")
+})
+@RequiresInstanceClassLoading
+public class SnowflakeComputingConnectionPool extends DBCPConnectionPool {
+
+public static final PropertyDescriptor SNOWFLAKE_URL = new
PropertyDescriptor.Builder()
+.displayName("Snowflake URL")
+.name("snowflake-url")
+.description("E.g.
'cb56215.europe-west2.gcp.snowflakecomputing.com/?db=MY_DB'." +
+" The '/?db=MY_DB' part can can have other connection parameters
as well." +
+" It can also be omitted but in that case tables need to be
referenced with fully qualified names e.g. 'MY_DB.PUBLIC.MY_TABLe'.")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.required(true)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_USER = new
PropertyDescriptor.Builder()
+.displayName("Snowflake User Name")
+.name("snowflake-user")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_PASSWORD = new
PropertyDescriptor.Builder()
+.displayName("Snowflake Password")
+
[GitHub] [nifi] tpalfy commented on a change in pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
tpalfy commented on a change in pull request #5692:
URL: https://github.com/apache/nifi/pull/5692#discussion_r793821940
##
File path:
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java
##
@@ -0,0 +1,314 @@
+/*
+ * 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.snowflake.service;
+
+import net.snowflake.client.jdbc.SnowflakeDriver;
+import org.apache.commons.dbcp2.BasicDataSource;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.DynamicProperties;
+import org.apache.nifi.annotation.behavior.DynamicProperty;
+import org.apache.nifi.annotation.behavior.RequiresInstanceClassLoading;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnDisabled;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.PropertyValue;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.dbcp.DBCPConnectionPool;
+import org.apache.nifi.expression.AttributeExpression;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.InitializationException;
+
+import java.sql.Connection;
+import java.sql.Driver;
+import java.sql.DriverManager;
+import java.sql.SQLException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Implementation of Database Connection Pooling Service for Snowflake.
+ * Apache DBCP is used for connection pooling functionality.
+ */
+@Tags({"snowflake", "dbcp", "jdbc", "database", "connection", "pooling",
"store"})
+@CapabilityDescription("Provides Snowflake Connection Pooling Service.
Connections can be asked from pool and returned after usage.")
+@DynamicProperties({
+@DynamicProperty(name = "JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.VARIABLE_REGISTRY,
+description = "Snowflake JDBC driver property name and value applied
to JDBC connections."),
+@DynamicProperty(name = "SENSITIVE.JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.NONE,
+description = "Snowflake JDBC driver property name prefixed with
'SENSITIVE.' handled as a sensitive property.")
+})
+@RequiresInstanceClassLoading
+public class SnowflakeComputingConnectionPool extends DBCPConnectionPool {
+
+public static final PropertyDescriptor SNOWFLAKE_URL = new
PropertyDescriptor.Builder()
+.displayName("Snowflake URL")
+.name("snowflake-url")
+.description("E.g.
'cb56215.europe-west2.gcp.snowflakecomputing.com/?db=MY_DB'." +
+" The '/?db=MY_DB' part can can have other connection parameters
as well." +
+" It can also be omitted but in that case tables need to be
referenced with fully qualified names e.g. 'MY_DB.PUBLIC.MY_TABLe'.")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.required(true)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_USER = new
PropertyDescriptor.Builder()
+.displayName("Snowflake User Name")
+.name("snowflake-user")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_PASSWORD = new
PropertyDescriptor.Builder()
+.displayName("Snowflake Password")
+
[jira] [Commented] (NIFI-9455) Add aggregated predictions to Prometheus Flow Metrics
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483271#comment-17483271 ] ASF subversion and git services commented on NIFI-9455: --- Commit 3ccc9d29b6653717f4d41ba1ef33f4ef20e77901 in nifi's branch refs/heads/main from Timea Barna [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3ccc9d2 ] NIFI-9455 Added aggregated predictions to Prometheus Flow Metrics This closes #5582 Signed-off-by: David Handermann > Add aggregated predictions to Prometheus Flow Metrics > - > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Minor > Fix For: 1.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add aggregated predictions to Prometheus Flow Metrics
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9455: --- Fix Version/s: 1.16.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add aggregated predictions to Prometheus Flow Metrics > - > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Minor > Fix For: 1.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add aggregated predictions to Prometheus
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9455: --- Priority: Minor (was: Major) > Add aggregated predictions to Prometheus > > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9455) Add aggregated predictions to Prometheus Flow Metrics
[ https://issues.apache.org/jira/browse/NIFI-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-9455: --- Summary: Add aggregated predictions to Prometheus Flow Metrics (was: Add aggregated predictions to Prometheus) > Add aggregated predictions to Prometheus Flow Metrics > - > > Key: NIFI-9455 > URL: https://issues.apache.org/jira/browse/NIFI-9455 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add aggregated prediction metrics to Prometheus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] exceptionfactory closed pull request #5582: NIFI-9455 Add aggregated predictions to Prometheus
exceptionfactory closed pull request #5582: URL: https://github.com/apache/nifi/pull/5582 -- 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 a change in pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
exceptionfactory commented on a change in pull request #5692:
URL: https://github.com/apache/nifi/pull/5692#discussion_r793802743
##
File path:
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java
##
@@ -0,0 +1,314 @@
+/*
+ * 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.snowflake.service;
+
+import net.snowflake.client.jdbc.SnowflakeDriver;
+import org.apache.commons.dbcp2.BasicDataSource;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.DynamicProperties;
+import org.apache.nifi.annotation.behavior.DynamicProperty;
+import org.apache.nifi.annotation.behavior.RequiresInstanceClassLoading;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnDisabled;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.PropertyValue;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.dbcp.DBCPConnectionPool;
+import org.apache.nifi.expression.AttributeExpression;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.InitializationException;
+
+import java.sql.Connection;
+import java.sql.Driver;
+import java.sql.DriverManager;
+import java.sql.SQLException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Implementation of Database Connection Pooling Service for Snowflake.
+ * Apache DBCP is used for connection pooling functionality.
+ */
+@Tags({"snowflake", "dbcp", "jdbc", "database", "connection", "pooling",
"store"})
+@CapabilityDescription("Provides Snowflake Connection Pooling Service.
Connections can be asked from pool and returned after usage.")
+@DynamicProperties({
+@DynamicProperty(name = "JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.VARIABLE_REGISTRY,
+description = "Snowflake JDBC driver property name and value applied
to JDBC connections."),
+@DynamicProperty(name = "SENSITIVE.JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.NONE,
+description = "Snowflake JDBC driver property name prefixed with
'SENSITIVE.' handled as a sensitive property.")
+})
+@RequiresInstanceClassLoading
+public class SnowflakeComputingConnectionPool extends DBCPConnectionPool {
+
+public static final PropertyDescriptor SNOWFLAKE_URL = new
PropertyDescriptor.Builder()
+.displayName("Snowflake URL")
+.name("snowflake-url")
+.description("E.g.
'cb56215.europe-west2.gcp.snowflakecomputing.com/?db=MY_DB'." +
+" The '/?db=MY_DB' part can can have other connection parameters
as well." +
+" It can also be omitted but in that case tables need to be
referenced with fully qualified names e.g. 'MY_DB.PUBLIC.MY_TABLe'.")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.required(true)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_USER = new
PropertyDescriptor.Builder()
+.displayName("Snowflake User Name")
+.name("snowflake-user")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_PASSWORD = new
PropertyDescriptor.Builder()
+.displayName("Snowflake Password")
+
[GitHub] [nifi] exceptionfactory commented on a change in pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
exceptionfactory commented on a change in pull request #5692:
URL: https://github.com/apache/nifi/pull/5692#discussion_r793802743
##
File path:
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java
##
@@ -0,0 +1,314 @@
+/*
+ * 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.snowflake.service;
+
+import net.snowflake.client.jdbc.SnowflakeDriver;
+import org.apache.commons.dbcp2.BasicDataSource;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.DynamicProperties;
+import org.apache.nifi.annotation.behavior.DynamicProperty;
+import org.apache.nifi.annotation.behavior.RequiresInstanceClassLoading;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnDisabled;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.PropertyValue;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.dbcp.DBCPConnectionPool;
+import org.apache.nifi.expression.AttributeExpression;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.InitializationException;
+
+import java.sql.Connection;
+import java.sql.Driver;
+import java.sql.DriverManager;
+import java.sql.SQLException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Implementation of Database Connection Pooling Service for Snowflake.
+ * Apache DBCP is used for connection pooling functionality.
+ */
+@Tags({"snowflake", "dbcp", "jdbc", "database", "connection", "pooling",
"store"})
+@CapabilityDescription("Provides Snowflake Connection Pooling Service.
Connections can be asked from pool and returned after usage.")
+@DynamicProperties({
+@DynamicProperty(name = "JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.VARIABLE_REGISTRY,
+description = "Snowflake JDBC driver property name and value applied
to JDBC connections."),
+@DynamicProperty(name = "SENSITIVE.JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.NONE,
+description = "Snowflake JDBC driver property name prefixed with
'SENSITIVE.' handled as a sensitive property.")
+})
+@RequiresInstanceClassLoading
+public class SnowflakeComputingConnectionPool extends DBCPConnectionPool {
+
+public static final PropertyDescriptor SNOWFLAKE_URL = new
PropertyDescriptor.Builder()
+.displayName("Snowflake URL")
+.name("snowflake-url")
+.description("E.g.
'cb56215.europe-west2.gcp.snowflakecomputing.com/?db=MY_DB'." +
+" The '/?db=MY_DB' part can can have other connection parameters
as well." +
+" It can also be omitted but in that case tables need to be
referenced with fully qualified names e.g. 'MY_DB.PUBLIC.MY_TABLe'.")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.required(true)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_USER = new
PropertyDescriptor.Builder()
+.displayName("Snowflake User Name")
+.name("snowflake-user")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_PASSWORD = new
PropertyDescriptor.Builder()
+.displayName("Snowflake Password")
+
[GitHub] [nifi] exceptionfactory commented on a change in pull request #5530: NIFI-9341 Adding record reader for CEF events
exceptionfactory commented on a change in pull request #5530:
URL: https://github.com/apache/nifi/pull/5530#discussion_r793722602
##
File path:
nifi-commons/nifi-record/src/main/java/org/apache/nifi/serialization/record/util/DataTypeUtils.java
##
@@ -2306,4 +2307,47 @@ public static boolean isFittingNumberType(final Object
value, final RecordFieldT
return false;
}
+
+public static DataType inferSimpleDataType(final String value) {
+if (value == null || value.isEmpty()) {
+return null;
+}
+
+if (NumberUtils.isParsable(value)) {
Review comment:
As mentioned in relation to the commons-lang3 dependency declaration,
this reference should be replaced with a direct check. Perhaps implementing a
simple check for null and empty, together with moving the Boolean string check
prior to this one would be sufficient? It would also be helpful to add a unit
test for this method.
##
File path:
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/cef/TestCEFUtil.java
##
@@ -0,0 +1,128 @@
+/*
+ * 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.cef;
+
+import org.apache.nifi.serialization.record.Record;
+import org.apache.nifi.serialization.record.RecordField;
+import org.apache.nifi.serialization.record.RecordFieldType;
+import org.junit.Assert;
+
+import java.sql.Timestamp;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Locale;
+import java.util.Map;
+
+public class TestCEFUtil {
+static final String RAW_FIELD = "raw";
+static final String RAW_VALUE = "Oct 12 04:16:11 localhost
CEF:0|Company|Product|1.2.3|audit-login|Successful login|3|";
+
+static final String INPUT_SINGLE_ROW_HEADER_FIELDS_ONLY =
"src/test/resources/cef/single-row-header-fields-only.txt";
+static final String INPUT_SINGLE_ROW_WITH_EXTENSIONS =
"src/test/resources/cef/single-row-with-extensions.txt";
+static final String INPUT_SINGLE_ROW_WITH_EMPTY_EXTENSION =
"src/test/resources/cef/single-row-with-empty-extension.txt";
+static final String INPUT_SINGLE_ROW_WITH_CUSTOM_EXTENSIONS =
"src/test/resources/cef/single-row-with-custom-extensions.txt";
+static final String INPUT_SINGLE_ROW_WITH_EMPTY_CUSTOM_EXTENSIONS =
"src/test/resources/cef/single-row-with-empty-custom-extensions.txt";
+static final String INPUT_SINGLE_ROW_WITH_INCORRECT_HEADER_FIELD =
"src/test/resources/cef/single-row-with-incorrect-header-field.txt";
+static final String INPUT_SINGLE_ROW_WITH_INCORRECT_CUSTOM_EXTENSIONS =
"src/test/resources/cef/single-row-with-incorrect-custom-extensions.txt";
+static final String INPUT_EMPTY_ROW =
"src/test/resources/cef/empty-row.txt";
+static final String INPUT_MISFORMATTED_ROW =
"src/test/resources/cef/misformatted-row.txt";
+static final String INPUT_MULTIPLE_IDENTICAL_ROWS =
"src/test/resources/cef/multiple-rows.txt";
+static final String INPUT_MULTIPLE_ROWS_WITH_DIFFERENT_CUSTOM_TYPES =
"src/test/resources/cef/multiple-rows-with-different-custom-types.txt";
+static final String INPUT_MULTIPLE_ROWS_STARTING_WITH_EMPTY_ROW =
"src/test/resources/cef/multiple-rows-starting-with-empty-row.txt";
+static final String INPUT_MULTIPLE_ROWS_WITH_EMPTY_ROWS =
"src/test/resources/cef/multiple-rows-with-empty-rows.txt";
+static final String
INPUT_MULTIPLE_ROWS_WITH_DECREASING_NUMBER_OF_EXTENSIONS =
"src/test/resources/cef/multiple-rows-decreasing-number-of-extensions.txt";
+static final String
INPUT_MULTIPLE_ROWS_WITH_INCREASING_NUMBER_OF_EXTENSIONS =
"src/test/resources/cef/multiple-rows-increasing-number-of-extensions.txt";
+
+static final Map EXPECTED_HEADER_VALUES = new HashMap<>();
+static final Map EXPECTED_EXTENSION_VALUES = new
HashMap<>();
+
+static final String CUSTOM_EXTENSION_FIELD_NAME = "loginsequence";
+static final RecordField CUSTOM_EXTENSION_FIELD = new
RecordField(TestCEFUtil.CUSTOM_EXTENSION_FIELD_NAME,
RecordFieldType.INT.getDataType());
+
[GitHub] [nifi] tpalfy commented on a change in pull request #5692: NIFI-9609 Added nifi-snowflake-bundle with a SnowflakeConnectionPool.
tpalfy commented on a change in pull request #5692:
URL: https://github.com/apache/nifi/pull/5692#discussion_r793742152
##
File path:
nifi-nar-bundles/nifi-snowflake-bundle/nifi-snowflake-services/src/main/java/org/apache/nifi/snowflake/service/SnowflakeComputingConnectionPool.java
##
@@ -0,0 +1,314 @@
+/*
+ * 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.snowflake.service;
+
+import net.snowflake.client.jdbc.SnowflakeDriver;
+import org.apache.commons.dbcp2.BasicDataSource;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.DynamicProperties;
+import org.apache.nifi.annotation.behavior.DynamicProperty;
+import org.apache.nifi.annotation.behavior.RequiresInstanceClassLoading;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnDisabled;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.PropertyValue;
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.dbcp.DBCPConnectionPool;
+import org.apache.nifi.expression.AttributeExpression;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.InitializationException;
+
+import java.sql.Connection;
+import java.sql.Driver;
+import java.sql.DriverManager;
+import java.sql.SQLException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Implementation of Database Connection Pooling Service for Snowflake.
+ * Apache DBCP is used for connection pooling functionality.
+ */
+@Tags({"snowflake", "dbcp", "jdbc", "database", "connection", "pooling",
"store"})
+@CapabilityDescription("Provides Snowflake Connection Pooling Service.
Connections can be asked from pool and returned after usage.")
+@DynamicProperties({
+@DynamicProperty(name = "JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.VARIABLE_REGISTRY,
+description = "Snowflake JDBC driver property name and value applied
to JDBC connections."),
+@DynamicProperty(name = "SENSITIVE.JDBC property name",
+value = "Snowflake JDBC property value",
+expressionLanguageScope = ExpressionLanguageScope.NONE,
+description = "Snowflake JDBC driver property name prefixed with
'SENSITIVE.' handled as a sensitive property.")
+})
+@RequiresInstanceClassLoading
+public class SnowflakeComputingConnectionPool extends DBCPConnectionPool {
+
+public static final PropertyDescriptor SNOWFLAKE_URL = new
PropertyDescriptor.Builder()
+.displayName("Snowflake URL")
+.name("snowflake-url")
+.description("E.g.
'cb56215.europe-west2.gcp.snowflakecomputing.com/?db=MY_DB'." +
+" The '/?db=MY_DB' part can can have other connection parameters
as well." +
+" It can also be omitted but in that case tables need to be
referenced with fully qualified names e.g. 'MY_DB.PUBLIC.MY_TABLe'.")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.required(true)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_USER = new
PropertyDescriptor.Builder()
+.displayName("Snowflake User Name")
+.name("snowflake-user")
+.defaultValue(null)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
+.build();
+
+public static final PropertyDescriptor SNOWFLAKE_PASSWORD = new
PropertyDescriptor.Builder()
+.displayName("Snowflake Password")
+
[GitHub] [nifi] exceptionfactory commented on a change in pull request #5530: NIFI-9341 Adding record reader for CEF events
exceptionfactory commented on a change in pull request #5530:
URL: https://github.com/apache/nifi/pull/5530#discussion_r793681389
##
File path:
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/java/org/apache/nifi/cef/ValidateLocale.java
##
@@ -0,0 +1,49 @@
+/*
+ * 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.cef;
+
+import org.apache.nifi.components.ValidationContext;
+import org.apache.nifi.components.ValidationResult;
+import org.apache.nifi.components.Validator;
+
+import java.util.Locale;
+
+/**
+ * This class is identical to {@code
org.apache.nifi.processors.standard.ParseCEF.ValidateLocale}.
Review comment:
Thanks for reply, that seems reasonable given the narrow scope of this
particular class.
--
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-1747) Send supported agent properties as part of the manifest
Adam Debreceni created MINIFICPP-1747: - Summary: Send supported agent properties as part of the manifest Key: MINIFICPP-1747 URL: https://issues.apache.org/jira/browse/MINIFICPP-1747 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Adam Debreceni Assignee: Adam Debreceni We should include in the manifest the properties supported by the agent, and possibly their types. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9559) Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED
[ https://issues.apache.org/jira/browse/NIFI-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483176#comment-17483176 ] Shawn Weeks commented on NIFI-9559: --- I will try and get an update to Zookeeper 3.7.0 pushed out this weekend. > Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED > -- > > Key: NIFI-9559 > URL: https://issues.apache.org/jira/browse/NIFI-9559 > Project: Apache NiFi > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Nathan Gough >Priority: Minor > Attachments: nifi_and_zookeeper_logs.txt > > > It's possible this is fixed in 1.15.2 but I don't see any commits that would > have resolved it. After a loss of connection to Zookeeper a NiFi node never > successfully reconnects to the Zookeeper or the Cluster and instead returns > errors about no Cluster Coordinator and a Session timeout has elapsed while > SUSPENDED repeatedly until you restart NiFi. > The error described is the same one at > https://issues.apache.org/jira/browse/CURATOR-405 however that patch has been > in NiFi for several versions now. > NiFi version is 1.14.0 and Zookeeper 3.6.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9633) Move Controller Service icons to the left-most column
John Wise created NIFI-9633: --- Summary: Move Controller Service icons to the left-most column Key: NIFI-9633 URL: https://issues.apache.org/jira/browse/NIFI-9633 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: John Wise NiFi tends to scale every single pop-up dialog across the entire width of a display. On larger displays, that requires the user to mouse around a lot in order to access some things. In particular, when working with Controller Services, the action icons on the far right are fairly cumbersome to access. Also, even when the Controller Service's row is highlighted, it's not always easy to determine that you're clicking on the right icons. Moving these icons to the left, with the Usage icon, would alleviate all of the extraneous mousing-around and make it easier to determine which icons are the correct ones for the Controller Service you need to interact with. I've already done this with some custom CSS, which helps immensely. Unfortunately, since our customer forbids (and prevents) the installation of browser extensions such as Stylish, I have to make these modifications every time we update NiFi. FWIW, similar updates to all of the pop-ups in both NiFi and NiFi Registry would greatly improve usability. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (NIFI-9559) Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED
[ https://issues.apache.org/jira/browse/NIFI-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483171#comment-17483171 ] Shawn Weeks edited comment on NIFI-9559 at 1/27/22, 2:23 PM: - Just wanted to add some details, first no I'm not using TLS between NiFi and Zookeeper nor any other authentication for Zookeeper. Second this morning after one of my nodes went down I went and reviewed the firewall logs and I noticed that when the issue occurs NiFi no longer even tries to talk to Zookeeper. After it starts throwing the error it just never connects. I still haven't had any luck forcing the issue to occur. I think you'd have to silently terminate the connection between Zookeeper and NiFi. Just virtually pulling the network plug on a NiFi VM doesn't seem to cause this. Sorry another note, I've been on NiFi 1.15.3 for about a week and seeing the exact same issue [~thenatog] was (Author: absolutesantaja): Just wanted to add some details, first no I'm not using TLS between NiFi and Zookeeper nor any other authentication for Zookeeper. Second this morning after one of my nodes went down I went and reviewed the firewall logs and I noticed that when the issue occurs NiFi no longer even tries to talk to Zookeeper. After it starts throwing the error it just never connects. I still haven't had any luck forcing the issue to occur. I think you'd have to silently terminate the connection between Zookeeper and NiFi. Just virtually pulling the network plug on a NiFi VM doesn't seem to cause this. [~thenatog] > Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED > -- > > Key: NIFI-9559 > URL: https://issues.apache.org/jira/browse/NIFI-9559 > Project: Apache NiFi > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Nathan Gough >Priority: Minor > Attachments: nifi_and_zookeeper_logs.txt > > > It's possible this is fixed in 1.15.2 but I don't see any commits that would > have resolved it. After a loss of connection to Zookeeper a NiFi node never > successfully reconnects to the Zookeeper or the Cluster and instead returns > errors about no Cluster Coordinator and a Session timeout has elapsed while > SUSPENDED repeatedly until you restart NiFi. > The error described is the same one at > https://issues.apache.org/jira/browse/CURATOR-405 however that patch has been > in NiFi for several versions now. > NiFi version is 1.14.0 and Zookeeper 3.6.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-3785) Allow user to move Controller Service
[ https://issues.apache.org/jira/browse/NIFI-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483173#comment-17483173 ] John Wise commented on NIFI-3785: - We typically create all of our controller services on the root canvas for reusability in all process groups, so I'd be happy with just a "Move to parent group" feature, similar to what's currently available for processors. If there's a need to move a controller service to any arbitrary process group, presenting the user with a drop-down list of named process groups to move it to might be sufficient for most people. > Allow user to move Controller Service > - > > Key: NIFI-3785 > URL: https://issues.apache.org/jira/browse/NIFI-3785 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Priority: Major > > Currently, there is no way to move a Controller Service from one Process > Group to another. I would like to be able to move a Controller Service from > its Process Group to the "parent" Process Group in order to broaden its scope. > The ability to move the Controller Service to a child group in order to > narrow its scope would be convenient as well but may be difficult to provide > an intuitive user experience around. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-9559) Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED
[ https://issues.apache.org/jira/browse/NIFI-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483171#comment-17483171 ] Shawn Weeks commented on NIFI-9559: --- Just wanted to add some details, first no I'm not using TLS between NiFi and Zookeeper nor any other authentication for Zookeeper. Second this morning after one of my nodes went down I went and reviewed the firewall logs and I noticed that when the issue occurs NiFi no longer even tries to talk to Zookeeper. After it starts throwing the error it just never connects. I still haven't had any luck forcing the issue to occur. I think you'd have to silently terminate the connection between Zookeeper and NiFi. Just virtually pulling the network plug on a NiFi VM doesn't seem to cause this. > Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED > -- > > Key: NIFI-9559 > URL: https://issues.apache.org/jira/browse/NIFI-9559 > Project: Apache NiFi > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Nathan Gough >Priority: Minor > Attachments: nifi_and_zookeeper_logs.txt > > > It's possible this is fixed in 1.15.2 but I don't see any commits that would > have resolved it. After a loss of connection to Zookeeper a NiFi node never > successfully reconnects to the Zookeeper or the Cluster and instead returns > errors about no Cluster Coordinator and a Session timeout has elapsed while > SUSPENDED repeatedly until you restart NiFi. > The error described is the same one at > https://issues.apache.org/jira/browse/CURATOR-405 however that patch has been > in NiFi for several versions now. > NiFi version is 1.14.0 and Zookeeper 3.6.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (NIFI-9559) Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED
[ https://issues.apache.org/jira/browse/NIFI-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483171#comment-17483171 ] Shawn Weeks edited comment on NIFI-9559 at 1/27/22, 2:20 PM: - Just wanted to add some details, first no I'm not using TLS between NiFi and Zookeeper nor any other authentication for Zookeeper. Second this morning after one of my nodes went down I went and reviewed the firewall logs and I noticed that when the issue occurs NiFi no longer even tries to talk to Zookeeper. After it starts throwing the error it just never connects. I still haven't had any luck forcing the issue to occur. I think you'd have to silently terminate the connection between Zookeeper and NiFi. Just virtually pulling the network plug on a NiFi VM doesn't seem to cause this. [~thenatog] was (Author: absolutesantaja): Just wanted to add some details, first no I'm not using TLS between NiFi and Zookeeper nor any other authentication for Zookeeper. Second this morning after one of my nodes went down I went and reviewed the firewall logs and I noticed that when the issue occurs NiFi no longer even tries to talk to Zookeeper. After it starts throwing the error it just never connects. I still haven't had any luck forcing the issue to occur. I think you'd have to silently terminate the connection between Zookeeper and NiFi. Just virtually pulling the network plug on a NiFi VM doesn't seem to cause this. > Zookeeper Client Can't Reconnect - Session timeout has elapsed while SUSPENDED > -- > > Key: NIFI-9559 > URL: https://issues.apache.org/jira/browse/NIFI-9559 > Project: Apache NiFi > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Nathan Gough >Priority: Minor > Attachments: nifi_and_zookeeper_logs.txt > > > It's possible this is fixed in 1.15.2 but I don't see any commits that would > have resolved it. After a loss of connection to Zookeeper a NiFi node never > successfully reconnects to the Zookeeper or the Cluster and instead returns > errors about no Cluster Coordinator and a Session timeout has elapsed while > SUSPENDED repeatedly until you restart NiFi. > The error described is the same one at > https://issues.apache.org/jira/browse/CURATOR-405 however that patch has been > in NiFi for several versions now. > NiFi version is 1.14.0 and Zookeeper 3.6.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-8040) Failed to update Flow on all nodes in cluster due to Cannot modify Processor configuration while the Processor is running
[ https://issues.apache.org/jira/browse/NIFI-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-8040: - Resolution: Fixed Status: Resolved (was: Patch Available) > Failed to update Flow on all nodes in cluster due to Cannot modify Processor > configuration while the Processor is running > - > > Key: NIFI-8040 > URL: https://issues.apache.org/jira/browse/NIFI-8040 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Vasily Gudoshnikov >Assignee: Mark Payne >Priority: Major > Labels: registry > Fix For: 1.16.0 > > Attachments: ProcessorNode.patch, image-2020-11-24-15-57-26-995.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Relates to NIFI-5227 > Steps to reproduce: > # Create a simple flow: *GenerateFlowFile + UpdateAttribute*. Ensure both > processors have valid state. > # Commit flow to a registry. > # Remove connection between processors or do something else to move > *UpdateAttribute* in invalid state. > # Commit flow to a registry. > # Change flow version to "1". *UpdateAttribute* should be valid now. > # Run *UpdateAttribute* > # Change flow version to "2". Ensure *UpdateAttribute* has invalid state now. > # Change flow version back to "1". > You will see error message _"Failed to update Flow on all nodes in cluster > due to Cannot modify Processor configuration while the Processor is running"._ > _!image-2020-11-24-15-57-26-995.png!_ > Error message for single node (non cluster) will be similar. > See attached patch. My solution is quite simple but I don't sure may be it is > not good enough. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] asfgit closed pull request #5718: NIFI-8040: When changing version of a flow, stop processors that have…
asfgit closed pull request #5718: URL: https://github.com/apache/nifi/pull/5718 -- 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 #5718: NIFI-8040: When changing version of a flow, stop processors that have…
pvillard31 commented on pull request #5718: URL: https://github.com/apache/nifi/pull/5718#issuecomment-1023246449 Merged, thanks @markap14 -- 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-8040) Failed to update Flow on all nodes in cluster due to Cannot modify Processor configuration while the Processor is running
[ https://issues.apache.org/jira/browse/NIFI-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483152#comment-17483152 ] ASF subversion and git services commented on NIFI-8040: --- Commit 3ea9faccc692554d5c352562e462cc1a8e06c177 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3ea9fac ] NIFI-8040: When changing version of a flow, stop processors that have a state of Starting in addition to those with a state of Running Signed-off-by: Pierre Villard This closes #5718. > Failed to update Flow on all nodes in cluster due to Cannot modify Processor > configuration while the Processor is running > - > > Key: NIFI-8040 > URL: https://issues.apache.org/jira/browse/NIFI-8040 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Vasily Gudoshnikov >Assignee: Mark Payne >Priority: Major > Labels: registry > Fix For: 1.16.0 > > Attachments: ProcessorNode.patch, image-2020-11-24-15-57-26-995.png > > Time Spent: 10m > Remaining Estimate: 0h > > Relates to NIFI-5227 > Steps to reproduce: > # Create a simple flow: *GenerateFlowFile + UpdateAttribute*. Ensure both > processors have valid state. > # Commit flow to a registry. > # Remove connection between processors or do something else to move > *UpdateAttribute* in invalid state. > # Commit flow to a registry. > # Change flow version to "1". *UpdateAttribute* should be valid now. > # Run *UpdateAttribute* > # Change flow version to "2". Ensure *UpdateAttribute* has invalid state now. > # Change flow version back to "1". > You will see error message _"Failed to update Flow on all nodes in cluster > due to Cannot modify Processor configuration while the Processor is running"._ > _!image-2020-11-24-15-57-26-995.png!_ > Error message for single node (non cluster) will be similar. > See attached patch. My solution is quite simple but I don't sure may be it is > not good enough. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (MINIFICPP-1735) Add Google Cloud Storage related processors
[ https://issues.apache.org/jira/browse/MINIFICPP-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink reassigned MINIFICPP-1735: -- Assignee: (was: Martin Zink) > Add Google Cloud Storage related processors > --- > > Key: MINIFICPP-1735 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1735 > Project: Apache NiFi MiNiFi C++ > Issue Type: Epic >Reporter: Martin Zink >Priority: Major > > Minifi already support AWS and Azure, but we currently lack the support for > Google Cloud Storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1746) Add ListGCSBucket processor
Martin Zink created MINIFICPP-1746: -- Summary: Add ListGCSBucket processor Key: MINIFICPP-1746 URL: https://issues.apache.org/jira/browse/MINIFICPP-1746 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Martin Zink Nifi's version https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-gcp-nar/1.5.0/org.apache.nifi.processors.gcp.storage.ListGCSBucket/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1745) Add DeleteGCSObject processor
Martin Zink created MINIFICPP-1745: -- Summary: Add DeleteGCSObject processor Key: MINIFICPP-1745 URL: https://issues.apache.org/jira/browse/MINIFICPP-1745 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Martin Zink Nifi's version: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-gcp-nar/1.5.0/org.apache.nifi.processors.gcp.storage.DeleteGCSObject/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1744) Add FetchGCSObject processor
Martin Zink created MINIFICPP-1744: -- Summary: Add FetchGCSObject processor Key: MINIFICPP-1744 URL: https://issues.apache.org/jira/browse/MINIFICPP-1744 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Martin Zink Nifi's version: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-gcp-nar/1.5.0/org.apache.nifi.processors.gcp.storage.FetchGCSObject/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1735) Add Google Cloud Storage related processors
[ https://issues.apache.org/jira/browse/MINIFICPP-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-1735: --- Epic Name: Google Cloud Storage support > Add Google Cloud Storage related processors > --- > > Key: MINIFICPP-1735 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1735 > Project: Apache NiFi MiNiFi C++ > Issue Type: Epic >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > > Minifi already support AWS and Azure, but we currently lack the support for > Google Cloud Storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MINIFICPP-1743) Add PutGCSObject processor
Martin Zink created MINIFICPP-1743: -- Summary: Add PutGCSObject processor Key: MINIFICPP-1743 URL: https://issues.apache.org/jira/browse/MINIFICPP-1743 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Martin Zink Assignee: Martin Zink Nifi's version: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-gcp-nar/1.5.0/org.apache.nifi.processors.gcp.storage.PutGCSObject/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1735) Add Google Cloud Storage related processors
[ https://issues.apache.org/jira/browse/MINIFICPP-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-1735: --- Issue Type: Epic (was: New Feature) > Add Google Cloud Storage related processors > --- > > Key: MINIFICPP-1735 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1735 > Project: Apache NiFi MiNiFi C++ > Issue Type: Epic >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > > Minifi already support AWS and Azure, but we currently lack the support for > Google Cloud Storage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MINIFICPP-1703) ExecuteScript error handling fix, more docs and tests
[ https://issues.apache.org/jira/browse/MINIFICPP-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink resolved MINIFICPP-1703. Resolution: Fixed https://github.com/apache/nifi-minifi-cpp/commit/d640a1ee6de8e6e229e06edba56e31181fd5aab8 > ExecuteScript error handling fix, more docs and tests > - > > Key: MINIFICPP-1703 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1703 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > The TestExecuteScriptProcessorWithLuaScript integration test is not included > in the CI, it has couple build/test errors, these should be fixed and enabled > on some CI. > It seems lua script errors dont cause exceptions (like they do in Nifi or in > python). This should fixed aswell. > We should also add some examples/documentations how to use it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MINIFICPP-1702) DefragmentText multiinput improvement
[ https://issues.apache.org/jira/browse/MINIFICPP-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink updated MINIFICPP-1702: --- Status: Patch Available (was: In Progress) https://github.com/apache/nifi-minifi-cpp/pull/1248 > DefragmentText multiinput improvement > - > > Key: MINIFICPP-1702 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1702 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > DefragmentText should hold N buffers instead of just one. > So it can be used with TailFile watching multiple files. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MINIFICPP-1727) Add ENABLE_LUA_SCRIPTING flag to docker
[ https://issues.apache.org/jira/browse/MINIFICPP-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zink resolved MINIFICPP-1727. Resolution: Fixed https://github.com/apache/nifi-minifi-cpp/commit/07fd64dfe83f23437f2ed2597740ae371e0c25ad > Add ENABLE_LUA_SCRIPTING flag to docker > --- > > Key: MINIFICPP-1727 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1727 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Minor > Time Spent: 2h 10m > Remaining Estimate: 0h > > Currently make docker doesnt use the -DENABLE_LUA_SCRIPTING cmake flag so it > is impossible to create a docker image with lua scripting enabled -- This message was sent by Atlassian Jira (v8.20.1#820001)
