[PR] MINIFICPP-2259 ProcessContext::getProperty should operate on raw poin… [nifi-minifi-cpp]
martinzink opened a new pull request, #1707: URL: https://github.com/apache/nifi-minifi-cpp/pull/1707 …ters Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] MINIFICPP-2264 GenerateFlowFile: 'Custom Text' should be reevaluated … [nifi-minifi-cpp]
martinzink opened a new pull request, #1706: URL: https://github.com/apache/nifi-minifi-cpp/pull/1706 …once per batch Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12506) /nifi-api/flow/metrics endpoint times out if flow is big
Timea Barna created NIFI-12506: -- Summary: /nifi-api/flow/metrics endpoint times out if flow is big Key: NIFI-12506 URL: https://issues.apache.org/jira/browse/NIFI-12506 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna Assignee: Timea Barna If a flow is relatively big 10K processors /nifi-api/flow/metrics endpoint times out if nifi.analytics.predict.enabled set to true as gathering predictions takes long. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12437] - Summary [nifi]
mcgilman commented on code in PR #8143:
URL: https://github.com/apache/nifi/pull/8143#discussion_r1423253506
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/summary/ui/connection-status-listing/connection-status-listing.component.spec.ts:
##
@@ -0,0 +1,38 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import { ComponentFixture, TestBed } from '@angular/core/testing';
+
+import { ConnectionStatusListing } from
'./connection-status-listing.component';
+
+describe('ConnectionStatusListingComponent', () => {
Review Comment:
This string does not align with the current component name.
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/summary/ui/processor-status-listing/processor-status-table/processor-status-table.component.html:
##
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Name
+
+{{ formatName(item) }}
+
+
+
+
+
+Type
+
+{{ formatType(item) }}
+
+
+
+
+
+Process Group
+
+{{ formatProcessGroup(item) }}
+
+
+
+
+
+Run
Status
+
+
+
+{{ formatRunStatus(item) }}
+
+
+
+({{ pg.activeThreadCount }}/{{
pg.terminatedThreadCount }})
+
+
+
+({{ pg.activeThreadCount }})
+
+
+
+
+
+
+
+
+
+
+
+
+In
+
+
+(Size)
+
+5 min
+
+
+
+{{ formatIn(item) }}
+
+
+
+
+
+
+
+
+Read
+
+|
+
+Write
+
+5 min
+
+
+
+{{ formatReadWrite(item) }}
+
+
+
+
+
+
+
+
+Out
+
+
+(Size)
+
+5 min
+
+
+
+{{ formatOut(item) }}
+
+
+
+
+
+
+
+
+Tasks
+
+|
+
[jira] [Updated] (NIFI-12445) Provenance Event Table
[ https://issues.apache.org/jira/browse/NIFI-12445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12445: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Provenance Event Table > -- > > Key: NIFI-12445 > URL: https://issues.apache.org/jira/browse/NIFI-12445 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Introduce capabilities to search provenance and view event listing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12445) Provenance Event Table
[ https://issues.apache.org/jira/browse/NIFI-12445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795524#comment-17795524 ] ASF subversion and git services commented on NIFI-12445: Commit 4f59f46ce4d95b23805643b8f6026b0cfc4ee59a in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4f59f46ce4 ] NIFI-12445: Provenance Event Listing (#8133) - Provenance Event Listing. - View Provenance Event dialog. - Provenance routing. - Provenance search. - Replay. - Download content. - View content. - Addressing review feedback. - Addressing review feedback. This closes #8133 > Provenance Event Table > -- > > Key: NIFI-12445 > URL: https://issues.apache.org/jira/browse/NIFI-12445 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Introduce capabilities to search provenance and view event listing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12445: Provenance Event Listing [nifi]
rfellows merged PR #8133: URL: https://github.com/apache/nifi/pull/8133 -- 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-12494) Broken CLI - jakarta.ws.rs.client.ClientBuilder cannot be found
[
https://issues.apache.org/jira/browse/NIFI-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795522#comment-17795522
]
Phil Lee commented on NIFI-12494:
-
Yeah, we use nifi-toolkit to populate nifi-registry with versioned flows and I
ran into this issue today when our team is trying to migrate to 2.0.
> Broken CLI - jakarta.ws.rs.client.ClientBuilder cannot be found
> ---
>
> Key: NIFI-12494
> URL: https://issues.apache.org/jira/browse/NIFI-12494
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 2.0.0-M1
>Reporter: Pierre Villard
>Priority: Blocker
> Fix For: 2.0.0
>
>
> When using the CLI, it currently throws the below error:
> {code:java}
> org.apache.nifi.toolkit.cli.api.CommandException: Error executing command
> 'pg-export' : java.lang.ClassNotFoundException: Provider for
> jakarta.ws.rs.client.ClientBuilder cannot be found
> at
> org.apache.nifi.toolkit.cli.impl.command.nifi.AbstractNiFiCommand.doExecute(AbstractNiFiCommand.java:65)
> at
> org.apache.nifi.toolkit.cli.impl.command.AbstractPropertyCommand.execute(AbstractPropertyCommand.java:74)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processCommand(CommandProcessor.java:248)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processGroupCommand(CommandProcessor.java:229)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.process(CommandProcessor.java:184)
> at org.apache.nifi.toolkit.cli.CLIMain.runSingleCommand(CLIMain.java:145)
> at org.apache.nifi.toolkit.cli.CLIMain.main(CLIMain.java:72)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Provider for jakarta.ws.rs.client.ClientBuilder cannot be found
> at jakarta.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:75)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient.(JerseyNiFiClient.java:98)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient$Builder.build(JerseyNiFiClient.java:345)
> at
> org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:169)
> at
> org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:59)
> at
> org.apache.nifi.toolkit.cli.impl.command.nifi.AbstractNiFiCommand.doExecute(AbstractNiFiCommand.java:62)
> ... 6 more
> Caused by: java.lang.ClassNotFoundException: Provider for
> jakarta.ws.rs.client.ClientBuilder cannot be found
> at jakarta.ws.rs.client.FactoryFinder.find(FactoryFinder.java:163)
> at jakarta.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:62)
> ... 11 more{code}
> Not sure which exact change caused this but it's likely related to some
> dependency management improvements we did.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12394) when importing versioned flow with InvokeHTTP, SSLContextService property is invalid
[
https://issues.apache.org/jira/browse/NIFI-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael W Moser updated NIFI-12394:
---
Description:
I built a Process Group containing one StandardRestrictedSSLContextService that
is referenced by an InvokeHTTP processor. I downloaded that Process Group as a
flow definition {*}with external services{*}. I also versioned that Process
Group in NiFi Registry.
Inside the flow definition, I see the StandardRestrictedSSLContextService with
"identifier":"d7d70b6c-abe4-3564-a219-b289cb7f25d2" and InvokeHTTP references
that UUID.
When I create a new Process Group using either the downloaded flow definition
or the NiFi Registry flow, a new StandardRestrictedSSLContextService is created
and it has a new UUID as expected. The InvokeHTTP processor is invalid because
it references the old StandardRestrictedSSLContextService UUID
d7d70b6c-abe4-3564-a219-b289cb7f25d2 which does not exist.
was:
I built a Process Group containing one StandardRestrictedSSLContextService that
is referenced by an InvokeHTTP and a ListenHTTP processor. I downloaded that
Process Group as a flow definition with external services. I also versioned
that Process Group in NiFi Registry.
Inside the flow definition, I see the StandardRestrictedSSLContextService with
"identifier":"d7d70b6c-abe4-3564-a219-b289cb7f25d2" and both InvokeHTTP and
ListenHTTP referencing that same UUID.
When I create a new Process Group using either the downloaded flow definition
or the NiFi Registry flow, the StandardRestrictedSSLContextService is invalid
as expected and it has a new UUID as expected. I enter the keystore and
truststore passwords and enable the service. Only one processor references the
new StandardRestrictedSSLContextService. The other processor is still invalid
because it references the old UUID d7d70b6c-abe4-3564-a219-b289cb7f25d2 which
does not exist.
edit: I tried this using a controller service that does not have sensitive
properties (XMLFileLookupService), and did not have this problem, so it could
be related to sensitive properties.
> when importing versioned flow with InvokeHTTP, SSLContextService property is
> invalid
>
>
> Key: NIFI-12394
> URL: https://issues.apache.org/jira/browse/NIFI-12394
> Project: Apache NiFi
> Issue Type: Bug
> Components: Flow Versioning
>Reporter: Michael W Moser
>Priority: Major
>
> I built a Process Group containing one StandardRestrictedSSLContextService
> that is referenced by an InvokeHTTP processor. I downloaded that Process
> Group as a flow definition {*}with external services{*}. I also versioned
> that Process Group in NiFi Registry.
> Inside the flow definition, I see the StandardRestrictedSSLContextService
> with "identifier":"d7d70b6c-abe4-3564-a219-b289cb7f25d2" and InvokeHTTP
> references that UUID.
> When I create a new Process Group using either the downloaded flow definition
> or the NiFi Registry flow, a new StandardRestrictedSSLContextService is
> created and it has a new UUID as expected. The InvokeHTTP processor is
> invalid because it references the old StandardRestrictedSSLContextService
> UUID d7d70b6c-abe4-3564-a219-b289cb7f25d2 which does not exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12394) when importing versioned flow with InvokeHTTP, SSLContextService property is invalid
[ https://issues.apache.org/jira/browse/NIFI-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael W Moser updated NIFI-12394: --- Summary: when importing versioned flow with InvokeHTTP, SSLContextService property is invalid (was: Versioned flow with multiple components referencing same controller service will only have 1 valid component after import) > when importing versioned flow with InvokeHTTP, SSLContextService property is > invalid > > > Key: NIFI-12394 > URL: https://issues.apache.org/jira/browse/NIFI-12394 > Project: Apache NiFi > Issue Type: Bug > Components: Flow Versioning >Reporter: Michael W Moser >Priority: Major > > I built a Process Group containing one StandardRestrictedSSLContextService > that is referenced by an InvokeHTTP and a ListenHTTP processor. I downloaded > that Process Group as a flow definition with external services. I also > versioned that Process Group in NiFi Registry. > Inside the flow definition, I see the StandardRestrictedSSLContextService > with "identifier":"d7d70b6c-abe4-3564-a219-b289cb7f25d2" and both InvokeHTTP > and ListenHTTP referencing that same UUID. > When I create a new Process Group using either the downloaded flow definition > or the NiFi Registry flow, the StandardRestrictedSSLContextService is invalid > as expected and it has a new UUID as expected. I enter the keystore and > truststore passwords and enable the service. Only one processor references > the new StandardRestrictedSSLContextService. The other processor is still > invalid because it references the old UUID > d7d70b6c-abe4-3564-a219-b289cb7f25d2 which does not exist. > edit: I tried this using a controller service that does not have sensitive > properties (XMLFileLookupService), and did not have this problem, so it could > be related to sensitive properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12437] - Summary [nifi]
mcgilman commented on PR #8143: URL: https://github.com/apache/nifi/pull/8143#issuecomment-1850739779 Reviewing... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12505) System Diagnostics
Rob Fellows created NIFI-12505: -- Summary: System Diagnostics Key: NIFI-12505 URL: https://issues.apache.org/jira/browse/NIFI-12505 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Fellows -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12504) Remaining Summary Pages (tabs)
[ https://issues.apache.org/jira/browse/NIFI-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12504: --- Description: The initial effort was getting quite large, so this story was meant to capture the remaining work: * input ports * output ports * remote process groups * process groups * connections * support for cluster-specific ui elements was: The initial effort was getting quite large, so this story was meant to capture the remaining work: * input ports * output ports * remote process groups * process groups * connections * System Diagnostics * support for cluster-specific ui elements > Remaining Summary Pages (tabs) > -- > > Key: NIFI-12504 > URL: https://issues.apache.org/jira/browse/NIFI-12504 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > > The initial effort was getting quite large, so this story was meant to > capture the remaining work: > * input ports > * output ports > * remote process groups > * process groups > * connections > * support for cluster-specific ui elements -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Rob Fellows 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-12504) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [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 *** support for cluster-specific ui elements * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement >
[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 ] Rob Fellows 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 *** support for cluster-specific ui elements * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [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 *** output ports *** remote process groups *** process groups *** connections *** System Diagnostics *** support for cluster-specific ui elements * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt
[jira] [Updated] (NIFI-12504) Remaining Summary Pages (tabs)
[ https://issues.apache.org/jira/browse/NIFI-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12504: --- Summary: Remaining Summary Pages (tabs) (was: Remaining Summary Pages (tabs), System Diagnostics) > Remaining Summary Pages (tabs) > -- > > Key: NIFI-12504 > URL: https://issues.apache.org/jira/browse/NIFI-12504 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > > The initial effort was getting quite large, so this story was meant to > capture the remaining work: > * input ports > * output ports > * remote process groups > * process groups > * connections > * System Diagnostics > * support for cluster-specific ui elements -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12504) Remaining Summary Pages (tabs), System Diagnostics
Rob Fellows created NIFI-12504: -- Summary: Remaining Summary Pages (tabs), System Diagnostics Key: NIFI-12504 URL: https://issues.apache.org/jira/browse/NIFI-12504 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Fellows Assignee: Rob Fellows The initial effort was getting quite large, so this story was meant to capture the remaining work: * input ports * output ports * remote process groups * process groups * connections * System Diagnostics * support for cluster-specific ui elements -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Rob Fellows 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 *** output ports *** remote process groups *** process groups *** connections *** System Diagnostics *** support for cluster-specific ui elements * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [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) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > 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] [Updated] (NIFI-12437) Summary page
[ https://issues.apache.org/jira/browse/NIFI-12437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12437: --- Status: Patch Available (was: In Progress) > Summary page > > > Key: NIFI-12437 > URL: https://issues.apache.org/jira/browse/NIFI-12437 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Build the Summary Page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12105) ExecuteStateless should support multiple directories for NAR Directory property
[ https://issues.apache.org/jira/browse/NIFI-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795481#comment-17795481 ] ASF subversion and git services commented on NIFI-12105: Commit a3e7998139f3c943339b05987ca568f5ff38723f in nifi's branch refs/heads/support/nifi-1.x from Peter Gyori [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a3e7998139 ] NIFI-12105: remove unnecessary checking of compressed content from testAdditionalNarDirectoriesSpecified test case This closes #8150. Signed-off-by: Peter Turcsanyi (cherry picked from commit 78b822c4520ff59653ffca1ca464a6919d000b03) > ExecuteStateless should support multiple directories for NAR Directory > property > --- > > Key: NIFI-12105 > URL: https://issues.apache.org/jira/browse/NIFI-12105 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions, NiFi Stateless >Reporter: Pierre Villard >Assignee: Peter Gyori >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > ExecuteStateless has a property for the NAR Directory which currently accepts > a single directory. When deploying custom NARs, it's usually done in a > dedicated directory that is not the lib directory. It'd be nice to support a > comma separated list of directories when configuring ExecuteStateless so that > the execute flow can reference custom NARs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12105: remove unnecessary checking of compressed content from te… [nifi]
asfgit closed pull request #8150: NIFI-12105: remove unnecessary checking of compressed content from te… URL: https://github.com/apache/nifi/pull/8150 -- 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-12105) ExecuteStateless should support multiple directories for NAR Directory property
[ https://issues.apache.org/jira/browse/NIFI-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795478#comment-17795478 ] ASF subversion and git services commented on NIFI-12105: Commit 78b822c4520ff59653ffca1ca464a6919d000b03 in nifi's branch refs/heads/main from Peter Gyori [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=78b822c452 ] NIFI-12105: remove unnecessary checking of compressed content from testAdditionalNarDirectoriesSpecified test case This closes #8150. Signed-off-by: Peter Turcsanyi > ExecuteStateless should support multiple directories for NAR Directory > property > --- > > Key: NIFI-12105 > URL: https://issues.apache.org/jira/browse/NIFI-12105 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions, NiFi Stateless >Reporter: Pierre Villard >Assignee: Peter Gyori >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > ExecuteStateless has a property for the NAR Directory which currently accepts > a single directory. When deploying custom NARs, it's usually done in a > dedicated directory that is not the lib directory. It'd be nice to support a > comma separated list of directories when configuring ExecuteStateless so that > the execute flow can reference custom NARs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] MINIFICPP-2258 Update LIBLZMA_URL [nifi-minifi-cpp]
fgerlits closed pull request #1704: MINIFICPP-2258 Update LIBLZMA_URL URL: https://github.com/apache/nifi-minifi-cpp/pull/1704 -- 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-1415 Pass references to onTrigger and onSchedule instead of… [nifi-minifi-cpp]
fgerlits closed pull request #1693: MINIFICPP-1415 Pass references to onTrigger and onSchedule instead of… URL: https://github.com/apache/nifi-minifi-cpp/pull/1693 -- 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=17795430#comment-17795430 ] David Handermann commented on NIFI-12501: - Thanks for the reply [~ferdei]. Regarding the items you listed: If you are leveraging the existing nifi-property-protection-cipher module, then supporting both sizes is fine as it is already implemented. If there are any new implementations, then simply restricting the supported options to AES-GCM 256 would be better and more straightforward. Regarding the key or password option, it is a bit confusing in the current implementation. I recommend only supporting one option or the other. In other words, it should require either a key, or a password from which to derive a key. The key derivation function in the existing command uses the scrypt algorithm, which is good, but it is only additional layer of complexity. It would be simpler to require a key of an exact size. Even better, using Java SecureRandom to generate a key without any user input seems like the best approach, and avoids some of the complexity of the existing implementation. > [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 > > 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] [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=17795422#comment-17795422 ] Ferenc Erdei commented on NIFI-12501: - Thanks [~szaszm] , This story is about encrypting the property files (so for example keystore/truststore passwords in the property files), not the flow. There was a separate story for the flow description and it works similarly to what you've just described. [~exceptionfactory] , The MiNiFi version of the toolkit will use the very same logic but on the same property file. * It will support only AES/GCM 128/256-bit algorithm * in the bootstrap.conf path is a mandatory parameter * optional output bootstrap conf path * hash / password is needed to encrypt the properties # The logic is to call the very same bootstrap transformer as you have in NiFi toolkit, to add(override) the root key to the bootstrap file if it doesn't contain it # Call the ApplicationPropertiesFileTransformer on the same file with AesGcmSensitivePropertyProvider Migration from an old key to a new root key works without extra parameters. It is read from the old bootstrap.conf if exists. > [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 > > 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] [Created] (NIFI-12503) Missing Documentation for nifi-api
Steven Matison created NIFI-12503: - Summary: Missing Documentation for nifi-api Key: NIFI-12503 URL: https://issues.apache.org/jira/browse/NIFI-12503 Project: Apache NiFi Issue Type: Improvement Reporter: Steven Matison Attachments: SAMSAL_0-1701894321710.png Community user has noticed that nifi-api docs are missing required request values. One such example is groupName on the api call for uploading process-groups: /process-groups/upload More dialouge and original conversation here: [https://community.cloudera.com/t5/Support-Questions/NIFI-API-REST-Upload-Json-definition-flow-file/m-p/380384#M244057] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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=17795417#comment-17795417 ] David Handermann commented on NIFI-12501: - Thanks for the additional background [~ferdei]. With that understanding, I agree that attempting to extend the current nifi-toolkit-encrypt-config as it stands does not sound like a good solution. Thanks for the note [~szaszm], is the a Jira to track the effort for MiNiFi C++? That sounds like a better approach in general. [~ferdei] In light of the fact that MiNiFi Java is already different enough from NiFi and NiFi Registry to warrant a separate implementation, I think it would be helpful to provide a basic outline of the implementation strategy. It could be in this Jira issue itself, but the order of operations and processing is very important when it comes to implementing encryption operations. It would be best to have the general steps outlined before putting together a pull request, otherwise, it may be require some things to be reworked in the course of the review. This is not an absolute requirement, but given the potential complexities, it seems like it would be helpful to provide a few more details of the proposed implementation to help the pull request review go more smoothly. > [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 > > 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] [Comment Edited] (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=17795414#comment-17795414 ] Marton Szasz edited comment on NIFI-12501 at 12/11/23 3:39 PM: --- In MiNiFi C\+\+, the approach will be to encrypt unencrypted sensitive properties in the flow definition on startup, but also provide a tool (encrypt-config option) to change them without ever writing the unencrypted value to disk. [~fgerlits] is working on the minifi c\+\+ effort. was (Author: szaszm): In MiNiFi C++, the approach will be to encrypt unencrypted sensitive properties in the flow definition on startup, but also provide a tool (encrypt-config option) to change them without ever writing the unencrypted value to disk. [~fgerlits] is working on the minifi c++ effort. > [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 > > 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] [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=17795414#comment-17795414 ] Marton Szasz commented on NIFI-12501: - In MiNiFi C++, the approach will be to encrypt unencrypted sensitive properties in the flow definition on startup, but also provide a tool (encrypt-config option) to change them without ever writing the unencrypted value to disk. [~fgerlits] is working on the minifi c++ effort. > [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 > > 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] [Created] (NIFI-12502) Processor Properties - Go To Parameter and Convert To Parameter
Matt Gilman created NIFI-12502: -- Summary: Processor Properties - Go To Parameter and Convert To Parameter Key: NIFI-12502 URL: https://issues.apache.org/jira/browse/NIFI-12502 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Update Processor Property configuration to support linking to a Parameter and converting to a Parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Matt Gilman 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) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [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) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link ** Convert to Parameter * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > 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) > * Counters (NIFI-12415) > * Bulletin Board > * Provenance (NIFI-12445) > ** Event
[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 ] Matt Gilman 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) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link ** Convert to Parameter * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [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) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * 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 ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link ** Convert to Parameter * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * 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 * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > 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) > * Counters (NIFI-12415) > * Bulletin Board > * Provenance (NIFI-12445) > ** Event Listing (NIFI-12445) > ** Search
[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=17795411#comment-17795411 ] Ferenc Erdei commented on NIFI-12501: - Thanks for the feedback [~exceptionfactory]. Unfortunately, at the moment the configuration structure of the MiNiFi is a little bit different from NiFi so we can not reuse the existing ApplicationPropertiesFileTransformer and BootstrapConfigurationFileTransformer. In MiNiFi the bootstrap.conf contains all of the properties, both bootstrap and minifi/nifi properties and the bootstrap code (re)generates the application property file (minifi.properties) during startup. This means that we need to encrypt only the properties in the bootstrap.conf file and write the root key there. As the current base classes are quite limited to the nifi/nifi registry bootstrap/application properties separation it doesn't make sense to make modifications there that would likely be removed shortly. The long-term goal is to eliminate this difference as well and have separate files with bootstrap only, and static minifi.properties file (it would match with NiFi). This would allow us to completely remove the above custom minifi-toolkit-encrypt-config and use the one that is provided in NiFi toolkit. Unfortunately, this requires a bigger refactor in the MiNiFi bootstrap around the configuration ingestors, but I can't work on it in the upcoming 1 or 2 months. I can create a separate follow-up Jira with the required work if that's fine for you. > [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 > > 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-12105: remove unnecessary checking of compressed content from te… [nifi]
pgyori commented on PR #8150: URL: https://github.com/apache/nifi/pull/8150#issuecomment-1850307509 Thank you @turcsanyip ! -- 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-12105: remove unnecessary checking of compressed content from te… [nifi]
pgyori opened a new pull request, #8150: URL: https://github.com/apache/nifi/pull/8150 …stAdditionalNarDirectoriesSpecified test case # Summary [NIFI-12105](https://issues.apache.org/jira/browse/NIFI-12105) # 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-12501) [MiNiFi] Encrypt MiNiFi bootstrap.conf properties
[ https://issues.apache.org/jira/browse/NIFI-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795408#comment-17795408 ] David Handermann commented on NIFI-12501: - [~ferdei] It would be worthwhile to evaluate the option of adding a MiNiFi mode to the existing encrypt-config toolkit. The current implementation supports both NiFi and NiFi Registry, based on one command line switch that enables different arguments. The updated implementation supports generalized transformer classes for properties files and XML files to cover standard formats. It may not make sense given that MiNiFi already has a separate toolkit, but it seems worth a basic evaluation. Alternatively, looking for ways to reuse some of the existing components in nifi-toolkit-encrypt-config module could be worthwhile. There are some limitations to the current approach in NiFi itself, but if an implementation for MiNiFi follows the same pattern and reuses code, that could provide for better refactoring down the road. > [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 > > 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] [Updated] (NIFI-12497) Upgrade snowflake-jdbc to 3.14.4
[
https://issues.apache.org/jira/browse/NIFI-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-12497:
--
Fix Version/s: 1.25.0
2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade snowflake-jdbc to 3.14.4
>
>
> Key: NIFI-12497
> URL: https://issues.apache.org/jira/browse/NIFI-12497
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 1.25.0, 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{snowflake-jdbc:3.14.4}} is supposed to fix issue with Java 21
> ([SNOW-917458|https://github.com/snowflakedb/snowflake-jdbc/issues/1512],
> NIFI-10883).
> Compatibility with {{snowflake-ingest-sdk}} has to be checked also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12497) Upgrade snowflake-jdbc to 3.14.4
[
https://issues.apache.org/jira/browse/NIFI-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795403#comment-17795403
]
ASF subversion and git services commented on NIFI-12497:
Commit 718d7e046143655e6b584342c5abaf6ef7bad2cb in nifi's branch
refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=718d7e0461 ]
NIFI-12497 Upgraded snowflake-jdbc to 3.14.4
Signed-off-by: Pierre Villard
This closes #8149.
> Upgrade snowflake-jdbc to 3.14.4
>
>
> Key: NIFI-12497
> URL: https://issues.apache.org/jira/browse/NIFI-12497
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{snowflake-jdbc:3.14.4}} is supposed to fix issue with Java 21
> ([SNOW-917458|https://github.com/snowflakedb/snowflake-jdbc/issues/1512],
> NIFI-10883).
> Compatibility with {{snowflake-ingest-sdk}} has to be checked also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12497) Upgrade snowflake-jdbc to 3.14.4
[
https://issues.apache.org/jira/browse/NIFI-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795404#comment-17795404
]
ASF subversion and git services commented on NIFI-12497:
Commit 148100b63b7e2108eb3b58e6071609233f017277 in nifi's branch
refs/heads/support/nifi-1.x from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=148100b63b ]
NIFI-12497 Upgraded snowflake-jdbc to 3.14.4
Signed-off-by: Pierre Villard
This closes #8149.
> Upgrade snowflake-jdbc to 3.14.4
>
>
> Key: NIFI-12497
> URL: https://issues.apache.org/jira/browse/NIFI-12497
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{snowflake-jdbc:3.14.4}} is supposed to fix issue with Java 21
> ([SNOW-917458|https://github.com/snowflakedb/snowflake-jdbc/issues/1512],
> NIFI-10883).
> Compatibility with {{snowflake-ingest-sdk}} has to be checked also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12497 Upgraded snowflake-jdbc to 3.14.4 [nifi]
asfgit closed pull request #8149: NIFI-12497 Upgraded snowflake-jdbc to 3.14.4 URL: https://github.com/apache/nifi/pull/8149 -- 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]
szaszm commented on code in PR #1681:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1681#discussion_r1422556409
##
bootstrap/system_dependency.py:
##
@@ -0,0 +1,55 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+from __future__ import annotations
+
+from typing import Dict, Set
+
+from minifi_option import MinifiOptions
+from package_manager import PackageManager
+
+
+def _create_system_dependencies(minifi_options: MinifiOptions) -> Dict[str,
Set[str]]:
+system_dependencies = {'patch': {'patch'}, 'make': {'make'}}
+if minifi_options.is_enabled("ENABLE_EXPRESSION_LANGUAGE"):
+system_dependencies['bison'] = {'bison'}
+system_dependencies['flex'] = {'flex'}
+if minifi_options.is_enabled("ENABLE_LIBARCHIVE"):
+system_dependencies['libarchive'] = {'libarchive'}
+if minifi_options.is_enabled("ENABLE_PCAP"):
+system_dependencies['libpcap'] = {'libpcap'}
+if minifi_options.is_enabled("ENABLE_USB_CAMERA"):
+system_dependencies['libusb'] = {'libusb'}
+system_dependencies['libpng'] = {'libpng'}
+if minifi_options.is_enabled("ENABLE_GPS"):
+system_dependencies['gpsd'] = {'gpsd'}
+if minifi_options.is_enabled("ENABLE_COAP"):
+system_dependencies['automake'] = {'automake'}
+system_dependencies['autoconf'] = {'autoconf'}
+system_dependencies['libtool'] = {'libtool'}
+if minifi_options.is_enabled("ENABLE_LUA_SCRIPTING"):
+system_dependencies['lua'] = {'lua'}
+if minifi_options.is_enabled("ENABLE_PYTHON_SCRIPTING"):
+system_dependencies['python'] = {'python'}
+if minifi_options.is_enabled("MINIFI_OPENSSL"):
+system_dependencies['openssl'] = {'perl'}
Review Comment:
OpenSSL also needs NASM, at least on Windows. Is it handled elsewhere?
##
bootstrap/py_bootstrap.bat:
##
@@ -0,0 +1,15 @@
+@echo off
+
+set SCRIPT_DIR=%~dp0
+set VENV_DIR=%SCRIPT_DIR%venv
+
+if exist %VENV_DIR% (
+call %VENV_DIR%\Scripts\activate
+) else (
+echo Creating virtualenv
+python -m venv %VENV_DIR%
+call %VENV_DIR%\Scripts\activate
+pip install -r %SCRIPT_DIR%requirements.txt
+)
+
+python %SCRIPT_DIR%main.py
Review Comment:
I like to use quotes, even when they're not strictly required. Windows cmd
scripts have a strange syntax, so you usually need to quote the whole argument,
not just the part containing the variable reference, otherwise the quotes just
become part of the argument.
```suggestion
set "SCRIPT_DIR=%~dp0"
set "VENV_DIR=%SCRIPT_DIR%venv"
if exist "%VENV_DIR%" (
call "%VENV_DIR%\Scripts\activate"
) else (
echo Creating virtualenv
python -m venv "%VENV_DIR%"
call "%VENV_DIR%\Scripts\activate"
pip install -r "%SCRIPT_DIR%requirements.txt"
)
python "%SCRIPT_DIR%main.py"
```
##
bootstrap/package_manager.py:
##
@@ -0,0 +1,325 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+import glob
+import os
+import platform
+import subprocess
+import sys
+import re
+from typing import Dict, Set
+
+from distro import distro
+
+
+def _query_yes_no(question: str, no_confirm: bool) -> bool:
+valid = {"yes": True, "y": True, "ye": True, "no": False, "n": False}
+
+if no_confirm:
+print("Running {} with noconfirm".format(question))
+return True
+while True:
+print("{} [y/n]".format(question))
+choice = input().lower()
+if choice in
Re: [PR] MINIFICPP-1797 Python bootstrap (part 1) [nifi-minifi-cpp]
lordgamez commented on code in PR #1681: URL: https://github.com/apache/nifi-minifi-cpp/pull/1681#discussion_r1422546555 ## bootstrap/system_dependency.py: ## @@ -0,0 +1,168 @@ +from __future__ import annotations + +import os +import platform +import sys +from typing import Dict + +import distro + +from minifi_option import MinifiOptions + + +def _query_yes_no(question: str, no_confirm: bool) -> bool: Review Comment: If it's minimal now I think that's okay -- 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]
szaszm commented on code in PR #1681:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1681#discussion_r1422537500
##
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:
We could do that. Automations could still explicitly set it to off if
needed. We should mention this in the readme if we change the default.
--
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-12501) [MiNiFi] Encrypt MiNiFi bootstrap.conf properties
Ferenc Erdei created NIFI-12501: --- Summary: [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 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-11308 Adding expression language function to return nifi version [nifi]
annanys23 commented on code in PR #8101:
URL: https://github.com/apache/nifi/pull/8101#discussion_r1422346949
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-nar-utils/src/main/java/org/apache/nifi/nar/NarClassLoaders.java:
##
@@ -74,6 +74,7 @@ private InitContext(
this.jettyBundle = jettyBundle;
this.serverInstance = serverInstance;
this.bundles = bundles;
+System.setProperty("nifi.version",
frameworkBundle.getBundleDetails().getCoordinate().getVersion());
Review Comment:
changed prop name to: nifi.framework.version and added a section to the
Expression Language Guide. Are there any other system properties that need to
be documented? I did not find any, outside of test classes.
--
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-12500) Support dynamic host/port in Set/Get SNMP processors
Lehel Boér created NIFI-12500: - Summary: Support dynamic host/port in Set/Get SNMP processors Key: NIFI-12500 URL: https://issues.apache.org/jira/browse/NIFI-12500 Project: Apache NiFi Issue Type: Improvement Reporter: Lehel Boér Assignee: Lehel Boér Currently GetSNMP initializes targets when the processor is first started. Supporting dynamic hosts makes it possible to read hosts from flowfiles and send SNMP GET requests to different targets dinamically. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12498) The Prioritization description in the User Guide is different from the actual source code implementation.
[
https://issues.apache.org/jira/browse/NIFI-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doin Cha updated NIFI-12498:
Component/s: Documentation & Website
> The Prioritization description in the User Guide is different from the actual
> source code implementation.
> -
>
> Key: NIFI-12498
> URL: https://issues.apache.org/jira/browse/NIFI-12498
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation Website
>Reporter: Doin Cha
>Priority: Minor
>
> In the prioritization explanation of the User Guide, it is stated that
> *OldestFlowFileFirstPrioritizer* is the _"default scheme that is used if no
> prioritizers are selected."_
> _([https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#prioritization)|https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#prioritization]_
>
>
> However, in the actual source code implementation, {color:#ff}*there is
> no automatic default setting when prioritizers are not selected.* {color}
> In such cases, the sorting is done by comparing the *ContentClaim* *of
> FlowFiles.*
> _([https://github.com/apache/nifi/blob/9a5ec83baa1b3593031f0917659a69e7a36bb0be/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/QueuePrioritizer.java#L39-L90])_
>
>
> It looks like the user guide needs to be revised.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12499) When the PublishKafka_2_6 processor attempts to publish, if any one of the FlowFiles fails, all of them are being forwarded to the failure queue.
Doin Cha created NIFI-12499:
---
Summary: When the PublishKafka_2_6 processor attempts to publish,
if any one of the FlowFiles fails, all of them are being forwarded to the
failure queue.
Key: NIFI-12499
URL: https://issues.apache.org/jira/browse/NIFI-12499
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: Doin Cha
When the PublishKafka processor is triggered, it uses
PublishKafkaUtil.pollFlowFiles() to read FlowFiles.
The problem is that {*}even if only one FlowFile fails to publish, the entire
FlowFile List is sent to the failure queue{*}.
As a result, even the successfully processed FlowFiles are being sent to the
failure queue. Is this the intended behavior?
If transactions are not being used, it seems more appropriate to forward only
the failed FlowFile to the failure queue.
(related source code :
[https://github.com/apache/nifi/blob/9a5ec83baa1b3593031f0917659a69e7a36bb0be/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-2-6-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/PublishKafka_2_6.java#L423)|https://github.com/apache/nifi/blob/9a5ec83baa1b3593031f0917659a69e7a36bb0be/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-2-6-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/PublishKafka_2_6.java#L423]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
