[jira] [Created] (NIFI-12658) Add an include list for users and / or groups when configuring ShellUserGroupProvider
Juan C. Sequeiros created NIFI-12658: Summary: Add an include list for users and / or groups when configuring ShellUserGroupProvider Key: NIFI-12658 URL: https://issues.apache.org/jira/browse/NIFI-12658 Project: Apache NiFi Issue Type: New Feature Reporter: Juan C. Sequeiros When setting up host to use sssd it is a general best practice to set the [pam] section of the sssd.conf file with value it might even be the default: enumerate = false This prevents the underlying commands to not return results. https://github.com/apache/nifi/blob/3fcf5f25b4c705f6909d058d81a7b8b6d6a648f1/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-shell-authorizer/src/main/java/org/apache/nifi/authorization/NssShellCommands.java#L29 in general: getent groups getent passwd Will only return local groups and users if the sssd.conf file has: enumarate = false However setting enumarate = true could give performance impact and underlying issues. Snippet from sssd.conf man pages: " enumerate (bool) Determines if a domain can be enumerated, that is, whether the domain can list all the users and group it contains. Note that it is not required to enable enumeration in order for secondary groups to be displayed. This parameter can have one of the following values: TRUE = Users and groups are enumerated FALSE = No enumerations for this domain Default: FALSE Enumerating a domain requires SSSD to download and store ALL user and group entries from the remote server. Note: Enabling enumeration has a moderate performance impact on SSSD while enumeration is running. It may take up to several minutes after SSSD startup to fully complete enumerations. During this time, individual requests for information will go directly to LDAP, though it may be slow, due to the heavy enumeration processing. Saving a large number of entries to cache after the enumeration completes might also be CPU intensive as the memberships have to be recomputed. This can lead to the “sssd_be” process becoming unresponsive or even restarted by the internal watchdog. While the first enumeration is running, requests for the complete user or group lists may return no results until it completes. Further, enabling enumeration may increase the time necessary to detect network disconnection, as longer timeouts are required to ensure that enumeration lookups are completed successfully. For more information, refer to the man pages for the specific id_provider in use. For the reasons cited above, enabling enumeration is not recommended, especially in large environments. " Propose to setting enumeration to instead introduce 2 additional property fields for UserGroupShellProvider to allow for: Include users Include Groups the same way that today it has the property settings for: public static final String EXCLUDE_USER_PROPERTY = "Exclude Users"; public static final String EXCLUDE_GROUP_PROPERTY = "Exclude Groups"; -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12657) Remove MiNiFi C2 Server Modules
[ https://issues.apache.org/jira/browse/NIFI-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809691#comment-17809691 ] ASF subversion and git services commented on NIFI-12657: Commit 3fcf5f25b4c705f6909d058d81a7b8b6d6a648f1 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3fcf5f25b4 ] NIFI-12657 Removed MiNiFi C2 Server modules This closes #8291. Signed-off-by: Joseph Witt > Remove MiNiFi C2 Server Modules > --- > > Key: NIFI-12657 > URL: https://issues.apache.org/jira/browse/NIFI-12657 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > The MiNiFi C2 server modules contain partial functionality migrated from the > historical MiNiFi Java repository. NIFI-9428 described a general effort to > implement C2 capabilities, but the task to implement a C2 server reference > implementation in NIFI-9533 was not completed. Rather than continuing to > maintain the partial implementation, the existing MiNiFi C2 server modules > should be removed from the main branch as part of general baseline efforts > for NiFi 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12657) Remove MiNiFi C2 Server Modules
[ https://issues.apache.org/jira/browse/NIFI-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-12657: Resolution: Fixed Status: Resolved (was: Patch Available) +1 merged to main > Remove MiNiFi C2 Server Modules > --- > > Key: NIFI-12657 > URL: https://issues.apache.org/jira/browse/NIFI-12657 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > The MiNiFi C2 server modules contain partial functionality migrated from the > historical MiNiFi Java repository. NIFI-9428 described a general effort to > implement C2 capabilities, but the task to implement a C2 server reference > implementation in NIFI-9533 was not completed. Rather than continuing to > maintain the partial implementation, the existing MiNiFi C2 server modules > should be removed from the main branch as part of general baseline efforts > for NiFi 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12657 Remove MiNiFi C2 Server modules [nifi]
asfgit closed pull request #8291: NIFI-12657 Remove MiNiFi C2 Server modules URL: https://github.com/apache/nifi/pull/8291 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12639 Ported all the changes from NIFI-11627 for the support/nifi-1.x branch [nifi]
exceptionfactory commented on code in PR #8274: URL: https://github.com/apache/nifi/pull/8274#discussion_r1462570649 ## nifi-nar-bundles/nifi-registry-bundle/nifi-registry-service/pom.xml: ## @@ -52,5 +52,20 @@ language governing permissions and limitations under the License. --> commons-io commons-io + +com.networknt +json-schema-validator +1.0.87 Review Comment: Thanks for the update. This one could go either way. For now, given just two references, it seems alright to leave it as it stands, but if there are any new modules that use it, it makes sense to promote it to a higher level. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12639 Ported all the changes from NIFI-11627 for the support/nifi-1.x branch [nifi]
dan-s1 commented on code in PR #8274: URL: https://github.com/apache/nifi/pull/8274#discussion_r1462523707 ## nifi-nar-bundles/nifi-registry-bundle/nifi-registry-service/pom.xml: ## @@ -52,5 +52,20 @@ language governing permissions and limitations under the License. --> commons-io commons-io + +com.networknt +json-schema-validator +1.0.87 Review Comment: Corrected. Should this dependency be pulled to a `` section in a parent common both to `nifi-nar-bundles/nifi-standard-bundle/pom.xml` and `nifi-nar-bundles/nifi-registry-bundle/nifi-registry-service/pom.xml`so the version could be specified only once? -- 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-12657) Remove MiNiFi C2 Server Modules
[ https://issues.apache.org/jira/browse/NIFI-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12657: Fix Version/s: 2.0.0-M2 Status: Patch Available (was: In Progress) > Remove MiNiFi C2 Server Modules > --- > > Key: NIFI-12657 > URL: https://issues.apache.org/jira/browse/NIFI-12657 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > The MiNiFi C2 server modules contain partial functionality migrated from the > historical MiNiFi Java repository. NIFI-9428 described a general effort to > implement C2 capabilities, but the task to implement a C2 server reference > implementation in NIFI-9533 was not completed. Rather than continuing to > maintain the partial implementation, the existing MiNiFi C2 server modules > should be removed from the main branch as part of general baseline efforts > for NiFi 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12657 Remove MiNiFi C2 Server modules [nifi]
exceptionfactory opened a new pull request, #8291: URL: https://github.com/apache/nifi/pull/8291 # Summary [NIFI-12657](https://issues.apache.org/jira/browse/NIFI-12657) Removes the `minifi-c2` bundle of modules containing the historical server capabilities migrated from the original MiNiFi Java repository. These server modules were not intended to serve as a reference implementation, and removing them from the repository will provide a better baseline for any future implementation. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12657) Remove MiNiFi C2 Server Modules
[ https://issues.apache.org/jira/browse/NIFI-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809664#comment-17809664 ] Joe Witt commented on NIFI-12657: - [~exceptionfactory] Thanks for capturing this and I agree with the assessment. It does not make sense to maintain a partial implementation especially for something that is meant as a reference implementation anyway. The c2 api allows others to build from and if a group becomes well motivated can have a fully maintained implementation here as well but this current model this doesn't tie fully into the ci/cd/build processes does not add value. Thanks! > Remove MiNiFi C2 Server Modules > --- > > Key: NIFI-12657 > URL: https://issues.apache.org/jira/browse/NIFI-12657 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > > The MiNiFi C2 server modules contain partial functionality migrated from the > historical MiNiFi Java repository. NIFI-9428 described a general effort to > implement C2 capabilities, but the task to implement a C2 server reference > implementation in NIFI-9533 was not completed. Rather than continuing to > maintain the partial implementation, the existing MiNiFi C2 server modules > should be removed from the main branch as part of general baseline efforts > for NiFi 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12657) Remove MiNiFi C2 Server Modules
David Handermann created NIFI-12657: --- Summary: Remove MiNiFi C2 Server Modules Key: NIFI-12657 URL: https://issues.apache.org/jira/browse/NIFI-12657 Project: Apache NiFi Issue Type: Improvement Components: MiNiFi Reporter: David Handermann Assignee: David Handermann The MiNiFi C2 server modules contain partial functionality migrated from the historical MiNiFi Java repository. NIFI-9428 described a general effort to implement C2 capabilities, but the task to implement a C2 server reference implementation in NIFI-9533 was not completed. Rather than continuing to maintain the partial implementation, the existing MiNiFi C2 server modules should be removed from the main branch as part of general baseline efforts for NiFi 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12639 Ported all the changes from NIFI-11627 for the support/nifi-1.x branch [nifi]
exceptionfactory commented on code in PR #8274: URL: https://github.com/apache/nifi/pull/8274#discussion_r1462484397 ## nifi-nar-bundles/nifi-registry-bundle/nifi-registry-service/pom.xml: ## @@ -52,5 +52,20 @@ language governing permissions and limitations under the License. --> commons-io commons-io + +com.networknt +json-schema-validator +1.0.87 Review Comment: This should be version `1.1.0`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12236 Improving fault tolerancy of the QuestDB backed metrics repository [nifi]
simonbence commented on PR #8152: URL: https://github.com/apache/nifi/pull/8152#issuecomment-1904912180 The failed checks look to be in connection with Python processors and minify -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-9677 Fixed LookupRecord issue that an empty JSON array caused mismatch [nifi]
mattyb149 commented on PR #8266:
URL: https://github.com/apache/nifi/pull/8266#issuecomment-1904858202
When running the unit tests with Java 8 (for a `support/nifi-1.x` backport),
I get an error because the `foo` entry shows up as `null` in the output of
`testLookupMissingJsonField()`:
`[{"foo":null,"unmentioned":{"foo":"original"}}]`
I checked some commits and everything looks the same, but I'm guessing there
was some change made to the record-based stuff in `main` that didn't make its
way back to the 1.x branch. Either way JSON is not guaranteed to have "ordered"
fields, so we should figure out why the `"foo": null` is in there (if it
shouldn't be) or check each field for its contents rather than the whole output
FlowFile.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Comment Edited] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809642#comment-17809642
]
Daniel Stieglitz edited comment on NIFI-11171 at 1/22/24 9:10 PM:
--
[~exceptionfactory]
The following processors use Jetty:
# HandleHttpRequest
# ListenHTTP
and the following supporting classes also use Jetty
# ListenHTTPServlet
# HttpProtocolStrategy
Both processors LogAttribute and LogMessage use a StringUtil class in Jetty
which I assume could be refactored to use Apache Commons StringUtils.
DId you still want these in a separate module?
was (Author: JIRAUSER294662):
[~exceptionfactory]
The following processors use Jetty:
# HandleHttpRequest
# ListenHTTP
and the following supporting classes also use Jetty
# ListenHTTPServlet
# HttpProtocolStrategy
Both processors LogAttribute and LogMessage use a StringUtil class in Jetty
which I assume could be refactored to use Apache Commons StringUtils.
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809642#comment-17809642
]
Daniel Stieglitz commented on NIFI-11171:
-
[~exceptionfactory]
The following processors use Jetty:
# HandleHttpRequest
# ListenHTTP
and the following supporting classes also use Jetty
# ListenHTTPServlet
# HttpProtocolStrategy
Both processors LogAttribute and LogMessage use a StringUtil class in Jetty
which I assume could be refactored to use Apache Commons StringUtils.
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809637#comment-17809637
]
Daniel Stieglitz edited comment on NIFI-11171 at 1/22/24 9:06 PM:
--
[~exceptionfactory]
The following processors use Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes also use Netty
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
was (Author: JIRAUSER294662):
[~exceptionfactory]
The following processors use Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809637#comment-17809637
]
Daniel Stieglitz edited comment on NIFI-11171 at 1/22/24 9:05 PM:
--
[~exceptionfactory]
The following processors use Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
was (Author: JIRAUSER294662):
[~exceptionfactory]
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809637#comment-17809637
]
Daniel Stieglitz edited comment on NIFI-11171 at 1/22/24 9:02 PM:
--
[~exceptionfactory]
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
was (Author: JIRAUSER294662):
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809637#comment-17809637
]
Daniel Stieglitz edited comment on NIFI-11171 at 1/22/24 8:45 PM:
--
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
and the following supporting classes
# RELPFrameDecoder
# RELPMessageChannelHandler
# RELPResponseEncoder
# RELPMessageServerFactory
DId you still want these in a separate module?
was (Author: JIRAUSER294662):
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
DId you still want these in a separate module?
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11171) Reorganize Standard Components for 2.0.0
[
https://issues.apache.org/jira/browse/NIFI-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809637#comment-17809637
]
Daniel Stieglitz commented on NIFI-11171:
-
For the Netty, I see the following processors using Netty:
# PutSyslog
# ListenRELP
# ListenSyslog
# ListenTCP
# PutSyslog
# PutTCP
DId you still want these in a separate module?
> Reorganize Standard Components for 2.0.0
>
>
> Key: NIFI-11171
> URL: https://issues.apache.org/jira/browse/NIFI-11171
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
>
> The {{nifi-standard-processors}} and {{nifi-standard-services}} modules
> include a large number of Processors and Controller Services supporting an
> array of capabilities. Some of these capabilities require specialized
> libraries that apply to a limited number of components.
> Moving Processors and Controller Services changes class names and bundle
> coordinates which will break existing flow configurations. For this reason,
> the selection of components for reorganization should be limited and focused.
> Components with less frequent updates or usage and components with large
> dependencies trees should be considered.
> The following items should be considered as described in the [NiFi 2.0
> Release
> Goals|https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals]:
> * SFTP Processors
> * Jolt Transform Processors
> * Jetty HTTP Processors
> * JSON Processors
> * Netty-based Processors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-12656) Upgrade vite to 4.5.2
[ https://issues.apache.org/jira/browse/NIFI-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12656. - Resolution: Fixed > Upgrade vite to 4.5.2 > - > > Key: NIFI-12656 > URL: https://issues.apache.org/jira/browse/NIFI-12656 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > The vite library supporting the new frontend build should be upgraded from > 4.5.1 to 4.5.2 to avoid unsafe URL matching in development environments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12656) Upgrade vite to 4.5.2
[ https://issues.apache.org/jira/browse/NIFI-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809620#comment-17809620 ] ASF subversion and git services commented on NIFI-12656: Commit 33c5f38687ce5d712b358d421624733239b2f0e3 in nifi's branch refs/heads/main from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=33c5f38687 ] NIFI-12656 Upgraded vite for new frontend from 4.5.1 to 4.5.2 This closes #8278 Signed-off-by: David Handermann > Upgrade vite to 4.5.2 > - > > Key: NIFI-12656 > URL: https://issues.apache.org/jira/browse/NIFI-12656 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > The vite library supporting the new frontend build should be upgraded from > 4.5.1 to 4.5.2 to avoid unsafe URL matching in development environments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12656 Bump vite from 4.5.1 to 4.5.2 in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi [nifi]
dependabot[bot] commented on PR #8278: URL: https://github.com/apache/nifi/pull/8278#issuecomment-1904701310 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12656 Bump vite from 4.5.1 to 4.5.2 in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi [nifi]
exceptionfactory closed pull request #8278: NIFI-12656 Bump vite from 4.5.1 to 4.5.2 in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi URL: https://github.com/apache/nifi/pull/8278 -- 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-12656) Upgrade vite to 4.5.2
David Handermann created NIFI-12656: --- Summary: Upgrade vite to 4.5.2 Key: NIFI-12656 URL: https://issues.apache.org/jira/browse/NIFI-12656 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0-M2 The vite library supporting the new frontend build should be upgraded from 4.5.1 to 4.5.2 to avoid unsafe URL matching in development environments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12650) Update json-path to 2.9.0
[ https://issues.apache.org/jira/browse/NIFI-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12650: Fix Version/s: 1.25.0 > Update json-path to 2.9.0 > - > > Key: NIFI-12650 > URL: https://issues.apache.org/jira/browse/NIFI-12650 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update json-path to 2.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12650) Update json-path to 2.9.0
[ https://issues.apache.org/jira/browse/NIFI-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809619#comment-17809619 ] ASF subversion and git services commented on NIFI-12650: Commit 594ae852e5864cde19a6abd9c422446073c99128 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=594ae852e5 ] NIFI-12650 Upgraded json-path from 2.8.0 to 2.9.0 (#8282) - Upgraded json-smart from 2.4.11 to 2.5.0 - Added json-path to managed dependencies in root Maven configuration - Suppressed OWASP Dependency Check finding resolved in json-path 2.9.0 (cherry picked from commit 93788f9281b63555f52a717bae7fe6ccc400b88d) > Update json-path to 2.9.0 > - > > Key: NIFI-12650 > URL: https://issues.apache.org/jira/browse/NIFI-12650 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update json-path to 2.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12653) Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2
[ https://issues.apache.org/jira/browse/NIFI-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809609#comment-17809609 ] ASF subversion and git services commented on NIFI-12653: Commit 27d57af45d2e39d75a4fa913bdba8a54918f6d05 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=27d57af45d ] NIFI-12653 Upgraded Spring from 6.0.15 to 6.0.16 - Upgraded Spring Boot from 3.2.0 to 3.2.2 for Registry Signed-off-by: Pierre Villard This closes #8284. > Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2 > --- > > Key: NIFI-12653 > URL: https://issues.apache.org/jira/browse/NIFI-12653 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded from 6.0.15 to 6.0.16, and > Spring Boot dependencies for NiFi Registry should be upgraded from 3.2.0 to > 3.2.2. > NiFi Registry currently uses Spring Framework 6.1, unlike other framework > components, due to an issue in nifi-web-api with AspectJ handling. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12653) Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2
[ https://issues.apache.org/jira/browse/NIFI-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12653: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2 > --- > > Key: NIFI-12653 > URL: https://issues.apache.org/jira/browse/NIFI-12653 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded from 6.0.15 to 6.0.16, and > Spring Boot dependencies for NiFi Registry should be upgraded from 3.2.0 to > 3.2.2. > NiFi Registry currently uses Spring Framework 6.1, unlike other framework > components, due to an issue in nifi-web-api with AspectJ handling. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12653 Upgrade Spring from 6.0.15 to 6.0.16 [nifi]
asfgit closed pull request #8284: NIFI-12653 Upgrade Spring from 6.0.15 to 6.0.16 URL: https://github.com/apache/nifi/pull/8284 -- 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-12654) Upgrade Netty to 4.1.106
[ https://issues.apache.org/jira/browse/NIFI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12654: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Netty to 4.1.106 > > > Key: NIFI-12654 > URL: https://issues.apache.org/jira/browse/NIFI-12654 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > Netty dependencies should be upgraded to 4.1.106 in order to resolve a > long-standing issue with HTTP/2 and large numbers of headers. > https://netty.io/news/2024/01/19/4-1-106-Final.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12654) Upgrade Netty to 4.1.106
[ https://issues.apache.org/jira/browse/NIFI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809606#comment-17809606 ] ASF subversion and git services commented on NIFI-12654: Commit 2a8fc71806989a6576c6affa091760ce27d29bff in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2a8fc71806 ] NIFI-12654 Upgraded Netty from 4.1.105 to 4.1.106 Signed-off-by: Pierre Villard This closes #8289. > Upgrade Netty to 4.1.106 > > > Key: NIFI-12654 > URL: https://issues.apache.org/jira/browse/NIFI-12654 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > Netty dependencies should be upgraded to 4.1.106 in order to resolve a > long-standing issue with HTTP/2 and large numbers of headers. > https://netty.io/news/2024/01/19/4-1-106-Final.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12654) Upgrade Netty to 4.1.106
[ https://issues.apache.org/jira/browse/NIFI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809605#comment-17809605 ] ASF subversion and git services commented on NIFI-12654: Commit e1eeed9c4665fa64f4c111dffc5d1196fd701f5d in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e1eeed9c46 ] NIFI-12654 Upgraded Netty from 4.1.105 to 4.1.106 Signed-off-by: Pierre Villard This closes #8289. > Upgrade Netty to 4.1.106 > > > Key: NIFI-12654 > URL: https://issues.apache.org/jira/browse/NIFI-12654 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > Netty dependencies should be upgraded to 4.1.106 in order to resolve a > long-standing issue with HTTP/2 and large numbers of headers. > https://netty.io/news/2024/01/19/4-1-106-Final.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12654 Upgrade Netty from 4.1.105 to 4.1.106 [nifi]
asfgit closed pull request #8289: NIFI-12654 Upgrade Netty from 4.1.105 to 4.1.106 URL: https://github.com/apache/nifi/pull/8289 -- 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-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809603#comment-17809603 ] ASF subversion and git services commented on NIFI-12652: Commit 088cbc5221f60d0643f5aaabe5977edf817ff772 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=088cbc5221 ] NIFI-12652 Upgraded SLF4J from 2.0.9 to 2.0.11 Signed-off-by: Pierre Villard This closes #8283. > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12652: -- Fix Version/s: 1.25.0 > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12652: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 20m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809600#comment-17809600 ] ASF subversion and git services commented on NIFI-12652: Commit a9f121c815b165841082916d45b65cf3a4a5e6c8 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a9f121c815 ] NIFI-12652 Upgraded SLF4J from 2.0.9 to 2.0.11 Signed-off-by: Pierre Villard This closes #8283. > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12652 Upgrade SLF4J from 2.0.9 to 2.0.11 [nifi]
asfgit closed pull request #8283: NIFI-12652 Upgrade SLF4J from 2.0.9 to 2.0.11 URL: https://github.com/apache/nifi/pull/8283 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service [nifi]
dependabot[bot] closed pull request #8290: Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service URL: https://github.com/apache/nifi/pull/8290 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service [nifi]
dependabot[bot] commented on PR #8290: URL: https://github.com/apache/nifi/pull/8290#issuecomment-1904556214 Looks like com.jayway.jsonpath:json-path is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-standard-bundle [nifi]
dependabot[bot] closed pull request #8288: Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-standard-bundle URL: https://github.com/apache/nifi/pull/8288 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils [nifi]
dependabot[bot] closed pull request #8287: Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils URL: https://github.com/apache/nifi/pull/8287 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-standard-bundle [nifi]
dependabot[bot] commented on PR #8288: URL: https://github.com/apache/nifi/pull/8288#issuecomment-1904555926 Looks like com.jayway.jsonpath:json-path is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils [nifi]
dependabot[bot] commented on PR #8287: URL: https://github.com/apache/nifi/pull/8287#issuecomment-1904555880 Looks like com.jayway.jsonpath:json-path is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-restapi-processors [nifi]
dependabot[bot] closed pull request #8286: Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-restapi-processors URL: https://github.com/apache/nifi/pull/8286 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-restapi-processors [nifi]
dependabot[bot] commented on PR #8286: URL: https://github.com/apache/nifi/pull/8286#issuecomment-1904555845 Looks like com.jayway.jsonpath:json-path is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-commons/nifi-expression-language [nifi]
dependabot[bot] closed pull request #8285: Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-commons/nifi-expression-language URL: https://github.com/apache/nifi/pull/8285 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-commons/nifi-expression-language [nifi]
dependabot[bot] commented on PR #8285: URL: https://github.com/apache/nifi/pull/8285#issuecomment-1904555786 Looks like com.jayway.jsonpath:json-path is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12650) Update json-path to 2.9.0
[ https://issues.apache.org/jira/browse/NIFI-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-12650: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update json-path to 2.9.0 > - > > Key: NIFI-12650 > URL: https://issues.apache.org/jira/browse/NIFI-12650 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update json-path to 2.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12650) Update json-path to 2.9.0
[ https://issues.apache.org/jira/browse/NIFI-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809596#comment-17809596 ] ASF subversion and git services commented on NIFI-12650: Commit 93788f9281b63555f52a717bae7fe6ccc400b88d in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=93788f9281 ] NIFI-12650 Upgraded json-path from 2.8.0 to 2.9.0 (#8282) - Upgraded json-smart from 2.4.11 to 2.5.0 - Added json-path to managed dependencies in root Maven configuration - Suppressed OWASP Dependency Check finding resolved in json-path 2.9.0 > Update json-path to 2.9.0 > - > > Key: NIFI-12650 > URL: https://issues.apache.org/jira/browse/NIFI-12650 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update json-path to 2.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12650 Upgrade json-path from 2.8.0 to 2.9.0 [nifi]
bbende merged PR #8282: URL: https://github.com/apache/nifi/pull/8282 -- 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-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12655) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Routing error handling * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417)
Re: [PR] NIFI-11520: Add a menu to display Flow Analysis report results [nifi]
tpalfy commented on code in PR #8273:
URL: https://github.com/apache/nifi/pull/8273#discussion_r1462197492
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/controllers/nf-ng-canvas-flow-status-controller.js:
##
@@ -400,6 +406,554 @@
}
}
+/**
+ * The flow analysis controller.
+ */
+
+this.flowAnalysis = {
+
+/**
+ * Create the list of rule violations
+ */
+buildRuleViolationsList: function(rules, violationsAndRecs) {
+var ruleViolationCountEl = $('#rule-violation-count');
+var ruleViolationListEl = $('#rule-violations-list');
+var ruleWarningCountEl = $('#rule-warning-count');
+var ruleWarningListEl = $('#rule-warnings-list');
+var violations = violationsAndRecs.filter(function
(violation) {
+return violation.enforcementPolicy === 'ENFORCE'
+});
+var warnings = violationsAndRecs.filter(function
(violation) {
+return violation.enforcementPolicy === 'WARN'
+});
+ruleViolationCountEl.empty().text('(' + violations.length
+ ')');
+ruleWarningCountEl.empty().text('(' + warnings.length +
')');
+ruleViolationListEl.empty();
+violations.forEach(function(violation) {
+var rule = rules.find(function(rule) {
+return rule.id === violation.ruleId;
+});
+// create DOM elements
+var violationListItemEl = $('');
+var violationEl = $('');
+var violationListItemWrapperEl = $('');
+var violationRuleEl = $('');
+var violationListItemNameEl = $('');
+var violationListItemIdEl = $('');
+var violationInfoButtonEl = $('');
+
+// add text content and button data
+$(violationRuleEl).text(rule.name);
+
$(violationListItemNameEl).text(violation.subjectDisplayName);
+$(violationListItemIdEl).text(violation.subjectId);
+
$(violationListItemEl).append(violationRuleEl).append(violationListItemWrapperEl);
+$(violationInfoButtonEl).data('violationInfo',
violation);
+
+// build list DOM structure
+
violationListItemWrapperEl.append(violationListItemNameEl).append(violationListItemIdEl);
+
violationEl.append(violationListItemWrapperEl).append(violationInfoButtonEl);
+
violationListItemEl.append(violationRuleEl).append(violationEl)
+ruleViolationListEl.append(violationListItemEl);
+});
+
+warnings.forEach(function(warning) {
+var rule = rules.find(function(rule) {
+return rule.id === warning.ruleId;
+});
+// create DOM elements
+var warningListItemEl = $('');
+var warningEl = $('');
+var warningListItemWrapperEl = $('');
+var warningRuleEl = $('');
+var warningListItemNameEl = $('');
+var warningListItemIdEl = $('');
+var warningInfoButtonEl = $('');
+
+// add text content and button data
+$(warningRuleEl).text(rule.name);
+
$(warningListItemNameEl).text(warning.subjectDisplayName);
+$(warningListItemIdEl).text(warning.subjectId);
+
$(warningListItemEl).append(warningRuleEl).append(warningListItemWrapperEl);
+$(warningInfoButtonEl).data('violationInfo', warning);
+
+// build list DOM structure
+
warningListItemWrapperEl.append(warningListItemNameEl).append(warningListItemIdEl);
+
warningEl.append(warningListItemWrapperEl).append(warningInfoButtonEl);
+
warningListItemEl.append(warningRuleEl).append(warningEl)
+ruleWarningListEl.append(warningListItemEl);
+});
+},
+
+/**
+ *
+ * Render a new list when it differs from the previous
violations response
+ */
+buildRuleViolations: function(rules, violations) {
+if
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Stop and Configure ** Open Custom UI ** Property History ** Unable to re-add any removed Property * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Better theme support (NIFI-12400) * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Routing error handling * Introduce header in new pages to unify with canvas and offer better navigation. (NIFI-12597) * Prompt user to save Parameter Context when Edit form is dirty * Start/Stop processors, process groups, ... (NIFI-12568) * Dialog vertical resizing on smaller screens do not allow users to access all fields (NIFI-12603) [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) * Counters (NIFI-12415) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers (NIFI-12622) * Cluster * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) * Help * About * Show Upstream/Downstream * Align * List Queue (NIFI-12589) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417)
[jira] [Created] (NIFI-12655) Better theme support
Scott Aslan created NIFI-12655: -- Summary: Better theme support Key: NIFI-12655 URL: https://issues.apache.org/jira/browse/NIFI-12655 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan Assignee: Scott Aslan The new ui is based on Angular Material components. We should follow the [https://v16.material.angular.io/guide/theming] and [https://v16.material.angular.io/guide/theming-your-components] guides as well as the Material design color system: [https://m2.material.io/design/color/the-color-system.html.|https://m2.material.io/design/color/the-color-system.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] MINIFICPP-2290 Support the default schema when serializing a JSON config [nifi-minifi-cpp]
fgerlits opened a new pull request, #1719: URL: https://github.com/apache/nifi-minifi-cpp/pull/1719 The JSON flow configuration comes in two flavors: the default schema and the NiFi schema. In the default schema, the root node location is `"."`, which is a notation borrowed from yaml-cpp to refer to the current node (so `node["."] == node`). This notation is not supported directly by rapidjson; it works when parsing the JSON input because it is implemented in `flow::Node::operator[]`. We need to handle `node["."]` when writing the JSON flow configuration, too. https://issues.apache.org/jira/browse/MINIFICPP-2290 --- 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)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service [nifi]
dependabot[bot] opened a new pull request, #8290: URL: https://github.com/apache/nifi/pull/8290 Bumps [com.jayway.jsonpath:json-path](https://github.com/jayway/JsonPath) from 2.8.0 to 2.9.0. Release notes Sourced from https://github.com/jayway/JsonPath/releases;>com.jayway.jsonpath:json-path's releases. json-path-2.9.0 What's Changed Fix for https://github.com/advisories/GHSA-pfh2-hfmq-phg5;>CVE-2023-51074. update dependencies by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/965;>json-path/JsonPath#965 JPMS: define Automatic-Module-Name as json.path by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/966;>json-path/JsonPath#966 Bump json-smart version from 2.4.10 to 2.5.0 by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/945;>json-path/JsonPath#945 Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md by https://github.com/lulunac27a;>@lulunac27a in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 [build] Remove deprecated gradle convetion usage by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/946;>json-path/JsonPath#946 Check for the existence of the next significant bracket by https://github.com/twobiers;>@twobiers in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Update versions by https://github.com/kallestenflo;>@kallestenflo in https://redirect.github.com/json-path/JsonPath/pull/987;>json-path/JsonPath#987 New Contributors https://github.com/lulunac27a;>@lulunac27a made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 https://github.com/twobiers;>@twobiers made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0 Commits https://github.com/json-path/JsonPath/commit/af7e516c69df680a6584fca7180ef082eb67c96c;>af7e516 Release 2.9.0 https://github.com/json-path/JsonPath/commit/af4dfcc17a9cb69002a5abc6e88a7745aef4c43d;>af4dfcc Make PropertyPathToken public, closes https://redirect.github.com/jayway/JsonPath/issues/955;>#955 https://github.com/json-path/JsonPath/commit/49b1151b11fbb147382c9c0f1c898b1ca0d2d3ec;>49b1151 Update versions (https://redirect.github.com/jayway/JsonPath/issues/987;>#987) https://github.com/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b;>71a09c1 Check for the existence of the next significant bracket (https://redirect.github.com/jayway/JsonPath/issues/985;>#985) https://github.com/json-path/JsonPath/commit/900ebfe58f4c9e78b209401c642320ef332ba618;>900ebfe Remove deprecated gradle usage (https://redirect.github.com/jayway/JsonPath/issues/946;>#946) https://github.com/json-path/JsonPath/commit/946274d3cb2ee51098bc0d8ba767a01da525218f;>946274d Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md... https://github.com/json-path/JsonPath/commit/425bcb18a5ffdfafcc60190c892f941ea4117fb7;>425bcb1 Bump json-smart version from 2.4.10 to 2.5.0 (https://redirect.github.com/jayway/JsonPath/issues/945;>#945) https://github.com/json-path/JsonPath/commit/2d57ab361512451fc3352816648357ffbd5c2a13;>2d57ab3 JPMS: define Automatic-Module-Name as json.path (https://redirect.github.com/jayway/JsonPath/issues/966;>#966) https://github.com/json-path/JsonPath/commit/1a57f7800b2c101b6fca218c3f04a8b6adf04122;>1a57f78 update dependencies (https://redirect.github.com/jayway/JsonPath/issues/965;>#965) https://github.com/json-path/JsonPath/commit/21de6207945dfca6b49809fa9dd08c3781b7ab9d;>21de620 Prepare next version See full diff in https://github.com/jayway/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to
[jira] [Updated] (NIFI-12654) Upgrade Netty to 4.1.106
[ https://issues.apache.org/jira/browse/NIFI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12654: Status: Patch Available (was: Open) > Upgrade Netty to 4.1.106 > > > Key: NIFI-12654 > URL: https://issues.apache.org/jira/browse/NIFI-12654 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Labels: backport-needed > Fix For: 1.25.0, 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > Netty dependencies should be upgraded to 4.1.106 in order to resolve a > long-standing issue with HTTP/2 and large numbers of headers. > https://netty.io/news/2024/01/19/4-1-106-Final.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12654 Upgrade Netty from 4.1.105 to 4.1.106 [nifi]
exceptionfactory opened a new pull request, #8289: URL: https://github.com/apache/nifi/pull/8289 # Summary [NIFI-12654](https://issues.apache.org/jira/browse/NIFI-12654) Upgrades Netty dependencies from 4.1.105 to [4.1.106](https://netty.io/news/2024/01/19/4-1-106-Final.html) resolving an HTTP/2 bug related to large numbers of headers. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12654) Upgrade Netty to 4.1.106
David Handermann created NIFI-12654: --- Summary: Upgrade Netty to 4.1.106 Key: NIFI-12654 URL: https://issues.apache.org/jira/browse/NIFI-12654 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Extensions Reporter: David Handermann Assignee: David Handermann Fix For: 1.25.0, 2.0.0-M2 Netty dependencies should be upgraded to 4.1.106 in order to resolve a long-standing issue with HTTP/2 and large numbers of headers. https://netty.io/news/2024/01/19/4-1-106-Final.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINIFICPP-2290) Support the default schema when serializing a JSON config
[
https://issues.apache.org/jira/browse/MINIFICPP-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenc Gerlits updated MINIFICPP-2290:
--
Summary: Support the default schema when serializing a JSON config (was:
Handle the default schema correctly when serializing a JSON config)
> Support the default schema when serializing a JSON config
> -
>
> Key: MINIFICPP-2290
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2290
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Ferenc Gerlits
>Assignee: Ferenc Gerlits
>Priority: Major
>
> The JSON flow configuration comes in two flavors: the default schema and the
> NiFi schema. In the default schema, the root node location is {{"."}}, which
> is a notation borrowed from yaml-cpp to refer to the current node (so
> {{node["."] == node}}).
> This notation is not supported directly by rapidjson; it works when parsing
> the JSON input because it is implemented in {{flow::Node::operator[]}}.
> We need to handle {{node["."]}} when writing the JSON flow configuration, too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MINIFICPP-2290) Handle the default schema correctly when serializing a JSON config
Ferenc Gerlits created MINIFICPP-2290:
-
Summary: Handle the default schema correctly when serializing a
JSON config
Key: MINIFICPP-2290
URL: https://issues.apache.org/jira/browse/MINIFICPP-2290
Project: Apache NiFi MiNiFi C++
Issue Type: Bug
Reporter: Ferenc Gerlits
Assignee: Ferenc Gerlits
The JSON flow configuration comes in two flavors: the default schema and the
NiFi schema. In the default schema, the root node location is {{"."}}, which
is a notation borrowed from yaml-cpp to refer to the current node (so
{{node["."] == node}}).
This notation is not supported directly by rapidjson; it works when parsing the
JSON input because it is implemented in {{flow::Node::operator[]}}.
We need to handle {{node["."]}} when writing the JSON flow configuration, too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-standard-bundle [nifi]
dependabot[bot] opened a new pull request, #8288: URL: https://github.com/apache/nifi/pull/8288 Bumps [com.jayway.jsonpath:json-path](https://github.com/jayway/JsonPath) from 2.8.0 to 2.9.0. Release notes Sourced from https://github.com/jayway/JsonPath/releases;>com.jayway.jsonpath:json-path's releases. json-path-2.9.0 What's Changed Fix for https://github.com/advisories/GHSA-pfh2-hfmq-phg5;>CVE-2023-51074. update dependencies by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/965;>json-path/JsonPath#965 JPMS: define Automatic-Module-Name as json.path by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/966;>json-path/JsonPath#966 Bump json-smart version from 2.4.10 to 2.5.0 by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/945;>json-path/JsonPath#945 Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md by https://github.com/lulunac27a;>@lulunac27a in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 [build] Remove deprecated gradle convetion usage by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/946;>json-path/JsonPath#946 Check for the existence of the next significant bracket by https://github.com/twobiers;>@twobiers in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Update versions by https://github.com/kallestenflo;>@kallestenflo in https://redirect.github.com/json-path/JsonPath/pull/987;>json-path/JsonPath#987 New Contributors https://github.com/lulunac27a;>@lulunac27a made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 https://github.com/twobiers;>@twobiers made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0 Commits https://github.com/json-path/JsonPath/commit/af7e516c69df680a6584fca7180ef082eb67c96c;>af7e516 Release 2.9.0 https://github.com/json-path/JsonPath/commit/af4dfcc17a9cb69002a5abc6e88a7745aef4c43d;>af4dfcc Make PropertyPathToken public, closes https://redirect.github.com/jayway/JsonPath/issues/955;>#955 https://github.com/json-path/JsonPath/commit/49b1151b11fbb147382c9c0f1c898b1ca0d2d3ec;>49b1151 Update versions (https://redirect.github.com/jayway/JsonPath/issues/987;>#987) https://github.com/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b;>71a09c1 Check for the existence of the next significant bracket (https://redirect.github.com/jayway/JsonPath/issues/985;>#985) https://github.com/json-path/JsonPath/commit/900ebfe58f4c9e78b209401c642320ef332ba618;>900ebfe Remove deprecated gradle usage (https://redirect.github.com/jayway/JsonPath/issues/946;>#946) https://github.com/json-path/JsonPath/commit/946274d3cb2ee51098bc0d8ba767a01da525218f;>946274d Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md... https://github.com/json-path/JsonPath/commit/425bcb18a5ffdfafcc60190c892f941ea4117fb7;>425bcb1 Bump json-smart version from 2.4.10 to 2.5.0 (https://redirect.github.com/jayway/JsonPath/issues/945;>#945) https://github.com/json-path/JsonPath/commit/2d57ab361512451fc3352816648357ffbd5c2a13;>2d57ab3 JPMS: define Automatic-Module-Name as json.path (https://redirect.github.com/jayway/JsonPath/issues/966;>#966) https://github.com/json-path/JsonPath/commit/1a57f7800b2c101b6fca218c3f04a8b6adf04122;>1a57f78 update dependencies (https://redirect.github.com/jayway/JsonPath/issues/965;>#965) https://github.com/json-path/JsonPath/commit/21de6207945dfca6b49809fa9dd08c3781b7ab9d;>21de620 Prepare next version See full diff in https://github.com/jayway/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to
[jira] [Updated] (NIFI-12653) Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2
[ https://issues.apache.org/jira/browse/NIFI-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12653: Fix Version/s: 2.0.0-M2 > Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2 > --- > > Key: NIFI-12653 > URL: https://issues.apache.org/jira/browse/NIFI-12653 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded from 6.0.15 to 6.0.16, and > Spring Boot dependencies for NiFi Registry should be upgraded from 3.2.0 to > 3.2.2. > NiFi Registry currently uses Spring Framework 6.1, unlike other framework > components, due to an issue in nifi-web-api with AspectJ handling. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12652: Labels: backport-needed (was: ) > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Time Spent: 10m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12652: Fix Version/s: 2.0.0-M2 > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 10m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils [nifi]
dependabot[bot] opened a new pull request, #8287: URL: https://github.com/apache/nifi/pull/8287 Bumps [com.jayway.jsonpath:json-path](https://github.com/jayway/JsonPath) from 2.8.0 to 2.9.0. Release notes Sourced from https://github.com/jayway/JsonPath/releases;>com.jayway.jsonpath:json-path's releases. json-path-2.9.0 What's Changed Fix for https://github.com/advisories/GHSA-pfh2-hfmq-phg5;>CVE-2023-51074. update dependencies by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/965;>json-path/JsonPath#965 JPMS: define Automatic-Module-Name as json.path by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/966;>json-path/JsonPath#966 Bump json-smart version from 2.4.10 to 2.5.0 by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/945;>json-path/JsonPath#945 Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md by https://github.com/lulunac27a;>@lulunac27a in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 [build] Remove deprecated gradle convetion usage by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/946;>json-path/JsonPath#946 Check for the existence of the next significant bracket by https://github.com/twobiers;>@twobiers in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Update versions by https://github.com/kallestenflo;>@kallestenflo in https://redirect.github.com/json-path/JsonPath/pull/987;>json-path/JsonPath#987 New Contributors https://github.com/lulunac27a;>@lulunac27a made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 https://github.com/twobiers;>@twobiers made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0 Commits https://github.com/json-path/JsonPath/commit/af7e516c69df680a6584fca7180ef082eb67c96c;>af7e516 Release 2.9.0 https://github.com/json-path/JsonPath/commit/af4dfcc17a9cb69002a5abc6e88a7745aef4c43d;>af4dfcc Make PropertyPathToken public, closes https://redirect.github.com/jayway/JsonPath/issues/955;>#955 https://github.com/json-path/JsonPath/commit/49b1151b11fbb147382c9c0f1c898b1ca0d2d3ec;>49b1151 Update versions (https://redirect.github.com/jayway/JsonPath/issues/987;>#987) https://github.com/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b;>71a09c1 Check for the existence of the next significant bracket (https://redirect.github.com/jayway/JsonPath/issues/985;>#985) https://github.com/json-path/JsonPath/commit/900ebfe58f4c9e78b209401c642320ef332ba618;>900ebfe Remove deprecated gradle usage (https://redirect.github.com/jayway/JsonPath/issues/946;>#946) https://github.com/json-path/JsonPath/commit/946274d3cb2ee51098bc0d8ba767a01da525218f;>946274d Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md... https://github.com/json-path/JsonPath/commit/425bcb18a5ffdfafcc60190c892f941ea4117fb7;>425bcb1 Bump json-smart version from 2.4.10 to 2.5.0 (https://redirect.github.com/jayway/JsonPath/issues/945;>#945) https://github.com/json-path/JsonPath/commit/2d57ab361512451fc3352816648357ffbd5c2a13;>2d57ab3 JPMS: define Automatic-Module-Name as json.path (https://redirect.github.com/jayway/JsonPath/issues/966;>#966) https://github.com/json-path/JsonPath/commit/1a57f7800b2c101b6fca218c3f04a8b6adf04122;>1a57f78 update dependencies (https://redirect.github.com/jayway/JsonPath/issues/965;>#965) https://github.com/json-path/JsonPath/commit/21de6207945dfca6b49809fa9dd08c3781b7ab9d;>21de620 Prepare next version See full diff in https://github.com/jayway/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to
[PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-restapi-processors [nifi]
dependabot[bot] opened a new pull request, #8286: URL: https://github.com/apache/nifi/pull/8286 Bumps [com.jayway.jsonpath:json-path](https://github.com/jayway/JsonPath) from 2.8.0 to 2.9.0. Release notes Sourced from https://github.com/jayway/JsonPath/releases;>com.jayway.jsonpath:json-path's releases. json-path-2.9.0 What's Changed Fix for https://github.com/advisories/GHSA-pfh2-hfmq-phg5;>CVE-2023-51074. update dependencies by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/965;>json-path/JsonPath#965 JPMS: define Automatic-Module-Name as json.path by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/966;>json-path/JsonPath#966 Bump json-smart version from 2.4.10 to 2.5.0 by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/945;>json-path/JsonPath#945 Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md by https://github.com/lulunac27a;>@lulunac27a in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 [build] Remove deprecated gradle convetion usage by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/946;>json-path/JsonPath#946 Check for the existence of the next significant bracket by https://github.com/twobiers;>@twobiers in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Update versions by https://github.com/kallestenflo;>@kallestenflo in https://redirect.github.com/json-path/JsonPath/pull/987;>json-path/JsonPath#987 New Contributors https://github.com/lulunac27a;>@lulunac27a made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 https://github.com/twobiers;>@twobiers made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0 Commits https://github.com/json-path/JsonPath/commit/af7e516c69df680a6584fca7180ef082eb67c96c;>af7e516 Release 2.9.0 https://github.com/json-path/JsonPath/commit/af4dfcc17a9cb69002a5abc6e88a7745aef4c43d;>af4dfcc Make PropertyPathToken public, closes https://redirect.github.com/jayway/JsonPath/issues/955;>#955 https://github.com/json-path/JsonPath/commit/49b1151b11fbb147382c9c0f1c898b1ca0d2d3ec;>49b1151 Update versions (https://redirect.github.com/jayway/JsonPath/issues/987;>#987) https://github.com/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b;>71a09c1 Check for the existence of the next significant bracket (https://redirect.github.com/jayway/JsonPath/issues/985;>#985) https://github.com/json-path/JsonPath/commit/900ebfe58f4c9e78b209401c642320ef332ba618;>900ebfe Remove deprecated gradle usage (https://redirect.github.com/jayway/JsonPath/issues/946;>#946) https://github.com/json-path/JsonPath/commit/946274d3cb2ee51098bc0d8ba767a01da525218f;>946274d Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md... https://github.com/json-path/JsonPath/commit/425bcb18a5ffdfafcc60190c892f941ea4117fb7;>425bcb1 Bump json-smart version from 2.4.10 to 2.5.0 (https://redirect.github.com/jayway/JsonPath/issues/945;>#945) https://github.com/json-path/JsonPath/commit/2d57ab361512451fc3352816648357ffbd5c2a13;>2d57ab3 JPMS: define Automatic-Module-Name as json.path (https://redirect.github.com/jayway/JsonPath/issues/966;>#966) https://github.com/json-path/JsonPath/commit/1a57f7800b2c101b6fca218c3f04a8b6adf04122;>1a57f78 update dependencies (https://redirect.github.com/jayway/JsonPath/issues/965;>#965) https://github.com/json-path/JsonPath/commit/21de6207945dfca6b49809fa9dd08c3781b7ab9d;>21de620 Prepare next version See full diff in https://github.com/jayway/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to
[PR] Bump com.jayway.jsonpath:json-path from 2.8.0 to 2.9.0 in /nifi-commons/nifi-expression-language [nifi]
dependabot[bot] opened a new pull request, #8285: URL: https://github.com/apache/nifi/pull/8285 Bumps [com.jayway.jsonpath:json-path](https://github.com/jayway/JsonPath) from 2.8.0 to 2.9.0. Release notes Sourced from https://github.com/jayway/JsonPath/releases;>com.jayway.jsonpath:json-path's releases. json-path-2.9.0 What's Changed Fix for https://github.com/advisories/GHSA-pfh2-hfmq-phg5;>CVE-2023-51074. update dependencies by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/965;>json-path/JsonPath#965 JPMS: define Automatic-Module-Name as json.path by https://github.com/SingingBush;>@SingingBush in https://redirect.github.com/json-path/JsonPath/pull/966;>json-path/JsonPath#966 Bump json-smart version from 2.4.10 to 2.5.0 by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/945;>json-path/JsonPath#945 Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md by https://github.com/lulunac27a;>@lulunac27a in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 [build] Remove deprecated gradle convetion usage by https://github.com/shoothzj;>@shoothzj in https://redirect.github.com/json-path/JsonPath/pull/946;>json-path/JsonPath#946 Check for the existence of the next significant bracket by https://github.com/twobiers;>@twobiers in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Update versions by https://github.com/kallestenflo;>@kallestenflo in https://redirect.github.com/json-path/JsonPath/pull/987;>json-path/JsonPath#987 New Contributors https://github.com/lulunac27a;>@lulunac27a made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/967;>json-path/JsonPath#967 https://github.com/twobiers;>@twobiers made their first contribution in https://redirect.github.com/json-path/JsonPath/pull/985;>json-path/JsonPath#985 Full Changelog: https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>https://github.com/json-path/JsonPath/compare/json-path-2.8.0...json-path-2.9.0 Commits https://github.com/json-path/JsonPath/commit/af7e516c69df680a6584fca7180ef082eb67c96c;>af7e516 Release 2.9.0 https://github.com/json-path/JsonPath/commit/af4dfcc17a9cb69002a5abc6e88a7745aef4c43d;>af4dfcc Make PropertyPathToken public, closes https://redirect.github.com/jayway/JsonPath/issues/955;>#955 https://github.com/json-path/JsonPath/commit/49b1151b11fbb147382c9c0f1c898b1ca0d2d3ec;>49b1151 Update versions (https://redirect.github.com/jayway/JsonPath/issues/987;>#987) https://github.com/json-path/JsonPath/commit/71a09c1193726c010917f1157ecbb069ad6c3e3b;>71a09c1 Check for the existence of the next significant bracket (https://redirect.github.com/jayway/JsonPath/issues/985;>#985) https://github.com/json-path/JsonPath/commit/900ebfe58f4c9e78b209401c642320ef332ba618;>900ebfe Remove deprecated gradle usage (https://redirect.github.com/jayway/JsonPath/issues/946;>#946) https://github.com/json-path/JsonPath/commit/946274d3cb2ee51098bc0d8ba767a01da525218f;>946274d Fixed rendering error on $..book[?(@.price = $['expensive'])] in README.md... https://github.com/json-path/JsonPath/commit/425bcb18a5ffdfafcc60190c892f941ea4117fb7;>425bcb1 Bump json-smart version from 2.4.10 to 2.5.0 (https://redirect.github.com/jayway/JsonPath/issues/945;>#945) https://github.com/json-path/JsonPath/commit/2d57ab361512451fc3352816648357ffbd5c2a13;>2d57ab3 JPMS: define Automatic-Module-Name as json.path (https://redirect.github.com/jayway/JsonPath/issues/966;>#966) https://github.com/json-path/JsonPath/commit/1a57f7800b2c101b6fca218c3f04a8b6adf04122;>1a57f78 update dependencies (https://redirect.github.com/jayway/JsonPath/issues/965;>#965) https://github.com/json-path/JsonPath/commit/21de6207945dfca6b49809fa9dd08c3781b7ab9d;>21de620 Prepare next version See full diff in https://github.com/jayway/JsonPath/compare/json-path-2.8.0...json-path-2.9.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to
[jira] [Updated] (NIFI-12653) Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2
[ https://issues.apache.org/jira/browse/NIFI-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12653: Status: Patch Available (was: Open) > Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2 > --- > > Key: NIFI-12653 > URL: https://issues.apache.org/jira/browse/NIFI-12653 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, NiFi Registry >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Spring Framework dependencies should be upgraded from 6.0.15 to 6.0.16, and > Spring Boot dependencies for NiFi Registry should be upgraded from 3.2.0 to > 3.2.2. > NiFi Registry currently uses Spring Framework 6.1, unlike other framework > components, due to an issue in nifi-web-api with AspectJ handling. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12652: Status: Patch Available (was: Open) > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12653 Upgrade Spring from 6.0.15 to 6.0.16 [nifi]
exceptionfactory opened a new pull request, #8284: URL: https://github.com/apache/nifi/pull/8284 # Summary [NIFI-12653](https://issues.apache.org/jira/browse/NIFI-12653) Upgrades Spring Framework dependencies from 6.0.15 to [6.0.16](https://github.com/spring-projects/spring-framework/releases/tag/v6.0.16) and upgrades Spring Boot from 3.2.0 to [3.2.2](https://github.com/spring-projects/spring-boot/releases/tag/v3.2.2) for NiFi Registry. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12653) Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2
David Handermann created NIFI-12653: --- Summary: Upgrade Spring Framework to 6.0.16 and Spring Boot to 3.2.2 Key: NIFI-12653 URL: https://issues.apache.org/jira/browse/NIFI-12653 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, NiFi Registry Reporter: David Handermann Assignee: David Handermann Spring Framework dependencies should be upgraded from 6.0.15 to 6.0.16, and Spring Boot dependencies for NiFi Registry should be upgraded from 3.2.0 to 3.2.2. NiFi Registry currently uses Spring Framework 6.1, unlike other framework components, due to an issue in nifi-web-api with AspectJ handling. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12652 Upgrade SLF4J from 2.0.9 to 2.0.11 [nifi]
exceptionfactory opened a new pull request, #8283: URL: https://github.com/apache/nifi/pull/8283 # Summary [NIFI-12652](https://issues.apache.org/jira/browse/NIFI-12652) Upgrades SLF4J libraries from 2.0.9 to [2.0.11](https://www.slf4j.org/news.html#2.0.11) incorporating some minor improvements to status reporting features. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12652) Upgrade SLF4J to 2.0.11
[ https://issues.apache.org/jira/browse/NIFI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12652: Summary: Upgrade SLF4J to 2.0.11 (was: Upgraded SLF4J to 2.0.11) > Upgrade SLF4J to 2.0.11 > --- > > Key: NIFI-12652 > URL: https://issues.apache.org/jira/browse/NIFI-12652 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > > SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some > minor improvements. > https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12652) Upgraded SLF4J to 2.0.11
David Handermann created NIFI-12652: --- Summary: Upgraded SLF4J to 2.0.11 Key: NIFI-12652 URL: https://issues.apache.org/jira/browse/NIFI-12652 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann SLF4J libraries should be upgraded from 2.0.9 to 2.0.11, which includes some minor improvements. https://www.slf4j.org/news.html#2.0.11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12650) Update json-path to 2.9.0
[ https://issues.apache.org/jira/browse/NIFI-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12650: Fix Version/s: 2.0.0-M2 Labels: backport-needed (was: ) Status: Patch Available (was: Open) > Update json-path to 2.9.0 > - > > Key: NIFI-12650 > URL: https://issues.apache.org/jira/browse/NIFI-12650 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M1 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Labels: backport-needed > Fix For: 2.0.0-M2 > > Time Spent: 1h > Remaining Estimate: 0h > > Update json-path to 2.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12650 Update json-path to 2.9.0 [nifi]
exceptionfactory commented on PR #8279: URL: https://github.com/apache/nifi/pull/8279#issuecomment-1904311360 @mr1716 In the process of further review, the best solution involved adding `json-path` to the set of dependencies managed at the root level. I submitted a new pull request implementing these changes in #8282, so I will close this one, but thank you for highlighting the upgrade! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12650 Update json-path to 2.9.0 [nifi]
exceptionfactory closed pull request #8279: NIFI-12650 Update json-path to 2.9.0 URL: https://github.com/apache/nifi/pull/8279 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12650 Upgrade json-path from 2.8.0 to 2.9.0 [nifi]
exceptionfactory opened a new pull request, #8282: URL: https://github.com/apache/nifi/pull/8282 # Summary [NIFI-12650](https://issues.apache.org/jira/browse/NIFI-12650) Upgrades `json-path` from 2.8.0 to [2.9.0](https://github.com/json-path/JsonPath/releases/tag/json-path-2.9.0) resolving CVE-2023-51074 related to a potential stack overflow with invalid inputs. Related upgrades include moving from json-smart 2.4.11 to [2.5.0](https://github.com/netplex/json-smart-v2/releases/tag/2.5.0). The upgrade moves `json-path` to a managed dependency at the root Maven configuration to cover both NiFi expression language, standard processors, and transitive dependencies in several modules. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12650 Update json-path to 2.9.0 [nifi]
exceptionfactory commented on PR #8279: URL: https://github.com/apache/nifi/pull/8279#issuecomment-1904251004 @mr1716 There are several transitive dependencies on `json-path` in some modules, so this looks like a case where a comprehensive upgrade is more involved. I am taking a closer look and evaluating options. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12643 Added support for FileResourceService in PutGCSObject [nifi]
balazsgerner opened a new pull request, #8281: URL: https://github.com/apache/nifi/pull/8281 # Summary Added support to upload content directly from local file's inputstream (by-passing the content repository) inside the PutGCSObject processor. The default behaviour is upload from flowfile content to be backward compatible. This can be overridden if the `RESOURCE_TRANSFER_SOURCE` property value is set to `FILE_RESOURCE_SERVICE`, and a `FileResourceService` controller service is registered. [NIFI-12643](https://issues.apache.org/jira/browse/NIFI-12643) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] MINIFICPP-1797 Python bootstrap (part 1) [nifi-minifi-cpp]
martinzink commented on code in PR #1681:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1681#discussion_r1461704026
##
bootstrap/cli.py:
##
@@ -0,0 +1,141 @@
+import os
+
+import inquirer
+
+from minifi_option import MinifiOptions
+from system_dependency import install_required
+
+
+def install_dependencies(minifi_options: MinifiOptions):
+install_required(minifi_options)
+
+
+def run_cmake(minifi_options: MinifiOptions):
+if not os.path.exists(minifi_options.build_dir):
+os.mkdir(minifi_options.build_dir)
+os.chdir(minifi_options.build_dir)
+cmake_cmd = f"cmake -G Ninja {minifi_options.create_cmake_options_str()}
{minifi_options.source_dir}"
Review Comment:
Changed the default,
https://github.com/apache/nifi-minifi-cpp/pull/1681/commits/0e43424c2a2f2567876534b06fa68ef005104874
But im not sure where (if at all) we should include this in the readme
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12650 Update json-path to 2.9.0 [nifi]
mr1716 commented on PR #8279: URL: https://github.com/apache/nifi/pull/8279#issuecomment-1903635512 @exceptionfactory thanks. Will update the PR shortly -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12651: Add case-insensitive field retrieval option for Record and Schema [nifi]
mark-bathori opened a new pull request, #8280: URL: https://github.com/apache/nifi/pull/8280 # Summary The idea is to create a separate map in the Schema with lowercase names and a separate method where the ‘fieldName’ parameter is also lowercased to make the retrieval case-insensitive. The new value map is created with **lazy evaluation** strategy so it’s only generated when there is a method call for it. With this approach we are not storing the same mapping twice. [NIFI-12651](https://issues.apache.org/jira/browse/NIFI-12651) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12651) Add case-insensitive field retrieval option for Record and Schema
Mark Bathori created NIFI-12651: --- Summary: Add case-insensitive field retrieval option for Record and Schema Key: NIFI-12651 URL: https://issues.apache.org/jira/browse/NIFI-12651 Project: Apache NiFi Issue Type: Improvement Reporter: Mark Bathori Assignee: Mark Bathori Currently the Record and Schema entities does not provide option to find fields in case-insensitive way. There are already a couple work-around in different modules so it would be useful to provide a common solution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12501 Encrypt MiNiFi bootstrap properties [nifi]
briansolo1985 commented on PR #8151: URL: https://github.com/apache/nifi/pull/8151#issuecomment-1903544615 Thanks for the updates. Looked good to me. Merged. -- 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-12501) [MiNiFi] Encrypt MiNiFi bootstrap.conf properties
[ https://issues.apache.org/jira/browse/NIFI-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809311#comment-17809311 ] ASF subversion and git services commented on NIFI-12501: Commit 5b9897cd4b343d0204cda103e2319cecad1fca99 in nifi's branch refs/heads/main from Ferenc Erdei [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5b9897cd4b ] NIFI-12501 Encrypt MiNiFi bootstrap properties Signed-off-by: Ferenc Kis This closes #8151. > [MiNiFi] Encrypt MiNiFi bootstrap.conf properties > - > > Key: NIFI-12501 > URL: https://issues.apache.org/jira/browse/NIFI-12501 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: Ferenc Erdei >Assignee: Ferenc Erdei >Priority: Major > Labels: minifi-java > Time Spent: 1h 40m > Remaining Estimate: 0h > > Currently, there is no way to encrypt sensitive properties in bootstrap.conf > and in the generated minifi.properties file. > The goal of this story is to make it possible to encrypt sensitive property > values in the bootstrap configuration file, and the generated > minifi.properties file also should contain only encrypted values. > * The supported encryption provider should be AES/GCM. > * The encryption key can be defined in the minifi.bootstrap.sensitive.key > property > * We should provide a tool(minifi-toolkit-encrypt-config) to encrypt the > bootstrap.conf properties, we can use the nifi-toolkit-encrypt-config as an > inspiration > Make sure that the solution works with change ingestors and c2 protocol as > well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12501) [MiNiFi] Encrypt MiNiFi bootstrap.conf properties
[ https://issues.apache.org/jira/browse/NIFI-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferenc Kis resolved NIFI-12501. --- Resolution: Fixed > [MiNiFi] Encrypt MiNiFi bootstrap.conf properties > - > > Key: NIFI-12501 > URL: https://issues.apache.org/jira/browse/NIFI-12501 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: Ferenc Erdei >Assignee: Ferenc Erdei >Priority: Major > Labels: minifi-java > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently, there is no way to encrypt sensitive properties in bootstrap.conf > and in the generated minifi.properties file. > The goal of this story is to make it possible to encrypt sensitive property > values in the bootstrap configuration file, and the generated > minifi.properties file also should contain only encrypted values. > * The supported encryption provider should be AES/GCM. > * The encryption key can be defined in the minifi.bootstrap.sensitive.key > property > * We should provide a tool(minifi-toolkit-encrypt-config) to encrypt the > bootstrap.conf properties, we can use the nifi-toolkit-encrypt-config as an > inspiration > Make sure that the solution works with change ingestors and c2 protocol as > well -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12501 Encrypt MiNiFi bootstrap properties [nifi]
briansolo1985 closed pull request #8151: NIFI-12501 Encrypt MiNiFi bootstrap properties URL: https://github.com/apache/nifi/pull/8151 -- 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
