[jira] [Created] (NIFI-12760) [MiNiFi] MiNiFi toolkit encrypt config should support encrypting flow.json.raw file
Ferenc Erdei created NIFI-12760: --- Summary: [MiNiFi] MiNiFi toolkit encrypt config should support encrypting flow.json.raw file Key: NIFI-12760 URL: https://issues.apache.org/jira/browse/NIFI-12760 Project: Apache NiFi Issue Type: Improvement Components: MiNiFi Reporter: Ferenc Erdei MiNiFi flows can be encrypted when downloading from ingestors or through c2 protocol, but when we edit it manually there is no way to encrypt sensitive properties. The nifi-toolkit-encrypt config supports encrypting the flow.json.gz, but it works only for this format. MiNiFi should provide a similar way to encrypt flows manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12236 Improving fault tolerancy of the QuestDB backed metrics repository [nifi]
exceptionfactory commented on code in PR #8152:
URL: https://github.com/apache/nifi/pull/8152#discussion_r1482432782
##
nifi-nar-bundles/nifi-questdb-bundle/nifi-questdb/src/test/java/org/apache/nifi/questdb/embedded/EmbeddedDatabaseManagerTest.java:
##
@@ -0,0 +1,397 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.questdb.embedded;
+
+import org.apache.commons.lang3.SystemUtils;
+import org.apache.nifi.questdb.Client;
+import org.apache.nifi.questdb.DatabaseException;
+import org.apache.nifi.questdb.DatabaseManager;
+import org.apache.nifi.questdb.mapping.RequestMapping;
+import org.apache.nifi.questdb.rollover.RolloverStrategy;
+import org.apache.nifi.questdb.util.Event;
+import org.apache.nifi.questdb.util.QuestDbTestUtil;
+import org.apache.nifi.util.file.FileUtils;
+import org.junit.jupiter.api.Disabled;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.Timeout;
+import org.junit.jupiter.api.condition.DisabledOnOs;
+import org.junit.jupiter.api.condition.OS;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.BufferedWriter;
+import java.io.File;
+import java.io.FileWriter;
+import java.io.IOException;
+import java.time.Instant;
+import java.time.temporal.ChronoUnit;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicReference;
+import java.util.stream.StreamSupport;
+
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT2_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT2_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.SELECT_QUERY;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getRandomTestData;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getTestData;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertIterableEquals;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+public class EmbeddedDatabaseManagerTest extends EmbeddedQuestDbTest {
+private static final Logger LOGGER =
LoggerFactory.getLogger(EmbeddedDatabaseManagerTest.class);
+private static final int DAYS_TO_KEEP_EVENT = 1;
+private static final String NON_EXISTING_PLACE = SystemUtils.IS_OS_WINDOWS
? "T:/nonExistingPlace" : "/nonExistingPlace";
+
+@Test
+public void testAcquiringWithoutInitialization() {
+final EmbeddedDatabaseManager testSubject = new
EmbeddedDatabaseManager(new SimpleEmbeddedDatabaseManagerContext());
+assertThrows(IllegalStateException.class, () ->
testSubject.acquireClient());
+}
+
+@Test
+public void testHappyPath() throws DatabaseException {
+final List testData = getTestData();
+final DatabaseManager testSubject = getTestSubject();
+assertDatabaseFolderIsNotEmpty();
+
+final Client client = testSubject.acquireClient();
+
+client.insert(EVENT_TABLE_NAME,
QuestDbTestUtil.getEventTableDataSource(testData));
+final List result = client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING));
+
+assertIterableEquals(testData, result);
+
+testSubject.close();
+
+// Even if the client itself is not connected, manager prevents client
to reach database after closing
+assertFalse(client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING)).iterator().hasNext());
+}
+
+@Test
+public void testRollover() throws DatabaseException, InterruptedException {
+final List testData = new ArrayList<>();
+testData.add(new Event(Instant.now().minus((DAYS_TO_KEEP_EVENT + 1),
ChronoUnit.DAYS), "A", 1));
+testData.add(new Event(Instant.now(), "B",
Re: [PR] NIFI-12697: Allow disabling scientific notation when writing JSON; us… [nifi]
Lehel44 commented on PR #8319: URL: https://github.com/apache/nifi/pull/8319#issuecomment-1933357560 Thanks @markap14 for making this. I went through the code and unit tests, as well did some manual testing and verifying property migrations. The changes made to the JsonWriter appear to function as intended. One concern is that while the changes to the JsonWriter fixed the scientific notation problem, the RecordReader still uses scientific notation by default. This mismatch could cause unexpected issues when using both components together. In my tests, I noticed that the `WriteJsonResult::writeRecord` received records in scientific notation, which might not be what users expect. To avoid confusion and ensure consistency, it would be wise to update the RecordReader to match the changes made to the JsonWriter. What do you think? -- 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-12759) RPG GoTo
Scott Aslan created NIFI-12759: -- Summary: RPG GoTo Key: NIFI-12759 URL: https://issues.apache.org/jira/browse/NIFI-12759 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan Assignee: Scott Aslan -- 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 ] 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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG (NIFI-12758) * Configure RPG * RPG Remote Ports * RPG Go To (NIFI-12759) * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * 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) * Flow Analysis report menu [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) ***
[jira] [Updated] (NIFI-12758) Create RPG
[ https://issues.apache.org/jira/browse/NIFI-12758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12758: --- Status: Patch Available (was: In Progress) > Create RPG > -- > > Key: NIFI-12758 > URL: https://issues.apache.org/jira/browse/NIFI-12758 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- 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 ] 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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG (NIFI-12758) * Configure RPG * RPG Remote Ports * RPG Go To * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * 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) * Flow Analysis report menu [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
[jira] [Created] (NIFI-12758) Create RPG
Scott Aslan created NIFI-12758: -- Summary: Create RPG Key: NIFI-12758 URL: https://issues.apache.org/jira/browse/NIFI-12758 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan Assignee: Scott Aslan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12757) Memory leak on Python side can result in OOMKiller killing python processes
[ https://issues.apache.org/jira/browse/NIFI-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-12757: -- Status: Patch Available (was: Open) > Memory leak on Python side can result in OOMKiller killing python processes > --- > > Key: NIFI-12757 > URL: https://issues.apache.org/jira/browse/NIFI-12757 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > There is a memory leak on the Python side that results in objects not being > properly cleaned up when transform method is invoked. This ultimately leads > to the Python process using large amounts of ram and often results in > OOMKiller killing the process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12757: Issue GC commands to Python for FlowFileTransformResults … [nifi]
markap14 opened a new pull request, #8375: URL: https://github.com/apache/nifi/pull/8375 …and RecordTransformResults when no longer needed on Java side # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 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-12757) Memory leak on Python side can result in OOMKiller killing python processes
Mark Payne created NIFI-12757: - Summary: Memory leak on Python side can result in OOMKiller killing python processes Key: NIFI-12757 URL: https://issues.apache.org/jira/browse/NIFI-12757 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 2.0.0 There is a memory leak on the Python side that results in objects not being properly cleaned up when transform method is invoked. This ultimately leads to the Python process using large amounts of ram and often results in OOMKiller killing the process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12756) Clarify in the NIFI Expression Language Documentation which Expressions can Throw Exceptions
Daniel Stieglitz created NIFI-12756: --- Summary: Clarify in the NIFI Expression Language Documentation which Expressions can Throw Exceptions Key: NIFI-12756 URL: https://issues.apache.org/jira/browse/NIFI-12756 Project: Apache NiFi Issue Type: Improvement Reporter: Daniel Stieglitz Assignee: Daniel Stieglitz In an effort to avoid issues as found in NIFI-5448 and NIFI-6344 the NIFI Expression Language documentation should be improved by highlighting which expressions could actually throw exceptions ultimately resulting in an admin yield. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12755 - Upgrade Jetty to 12.0.6 [nifi]
pvillard31 commented on PR #8374: URL: https://github.com/apache/nifi/pull/8374#issuecomment-1932951886 https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.6 -- 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-12755 - Upgrade Jetty to 12.0.6 [nifi]
pvillard31 opened a new pull request, #8374: URL: https://github.com/apache/nifi/pull/8374 # Summary [NIFI-12755](https://issues.apache.org/jira/browse/NIFI-12755) - Upgrade Jetty to 12.0.6 # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 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-12755) Upgrade Jetty to 12.0.6
[ https://issues.apache.org/jira/browse/NIFI-12755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12755: -- Status: Patch Available (was: Open) > Upgrade Jetty to 12.0.6 > --- > > Key: NIFI-12755 > URL: https://issues.apache.org/jira/browse/NIFI-12755 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 2.0.0 > > > Upgrade Jetty from 12.0.5 to 12.0.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12755) Upgrade Jetty to 12.0.6
Pierre Villard created NIFI-12755: - Summary: Upgrade Jetty to 12.0.6 Key: NIFI-12755 URL: https://issues.apache.org/jira/browse/NIFI-12755 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Pierre Villard Assignee: Pierre Villard Fix For: 2.0.0 Upgrade Jetty from 12.0.5 to 12.0.6 -- 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-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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies ** Status History * 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) * Flow Analysis report menu [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
Re: [PR] NIFI-12742: Error Handling in Summary, Users, and Queue Listing [nifi]
rfellows commented on PR #8366: URL: https://github.com/apache/nifi/pull/8366#issuecomment-1932878995 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] [Updated] (NIFI-12748) BUG - snackbar action button text in light mode is too dark
[ https://issues.apache.org/jira/browse/NIFI-12748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12748: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > BUG - snackbar action button text in light mode is too dark > --- > > Key: NIFI-12748 > URL: https://issues.apache.org/jira/browse/NIFI-12748 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0 > > Attachments: Screenshot 2024-02-06 at 4.02.36 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > !Screenshot 2024-02-06 at 4.02.36 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12748) BUG - snackbar action button text in light mode is too dark
[ https://issues.apache.org/jira/browse/NIFI-12748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815423#comment-17815423 ] ASF subversion and git services commented on NIFI-12748: Commit 43276acf55330033ccb433243a0657268d80f7d2 in nifi's branch refs/heads/main from Scott Aslan [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=43276acf55 ] [NIFI-12748] apply panelClass to snackbars to apply lighter color to … (#8365) * [NIFI-12748] apply panelClass to snackbars to apply lighter color to the snackbar action text * hover color for snackbar action button * updates based on https://github.com/angular/components/issues/11426 This closes #8365 > BUG - snackbar action button text in light mode is too dark > --- > > Key: NIFI-12748 > URL: https://issues.apache.org/jira/browse/NIFI-12748 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-02-06 at 4.02.36 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > !Screenshot 2024-02-06 at 4.02.36 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12748] apply panelClass to snackbars to apply lighter color to … [nifi]
rfellows merged PR #8365: URL: https://github.com/apache/nifi/pull/8365 -- 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-12753 updating various github actions versions [nifi]
joewitt commented on PR #8373: URL: https://github.com/apache/nifi/pull/8373#issuecomment-1932802398 I'm not sure on next steps for codecov. I see how to get our apache/nifi token but not familiar with next steps. -- 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-12665) Fetch dialog for Parameter Providers
[ https://issues.apache.org/jira/browse/NIFI-12665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12665: --- Status: Patch Available (was: In Progress) > Fetch dialog for Parameter Providers > > > Key: NIFI-12665 > URL: https://issues.apache.org/jira/browse/NIFI-12665 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Implement the dialog that fetches parameters from a provider and maps them to > a parameter context. -- 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-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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History (NIFI-12754) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies * 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) * Flow Analysis report menu [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
[jira] [Created] (NIFI-12754) Flow Configuration History
Rob Fellows created NIFI-12754: -- Summary: Flow Configuration History Key: NIFI-12754 URL: https://issues.apache.org/jira/browse/NIFI-12754 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Fellows Assignee: Rob Fellows -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12752) Update GitHub Workflows using macOS 14
[ https://issues.apache.org/jira/browse/NIFI-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12752: Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Update GitHub Workflows using macOS 14 > --- > > Key: NIFI-12752 > URL: https://issues.apache.org/jira/browse/NIFI-12752 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > GitHub recently [released macOS > 14|https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/] > as a build platform for GitHub Actions. > The macOS 14 runner uses the Apple Silicon M1 Processor. This has the > advantage of testing build behavior on the AArch64 platform, which includes > performance benefits in some cases. > The ci-workflow and system-tests build configurations should be updated to > use macOS 14 to provide regular evaluation of behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12752) Update GitHub Workflows using macOS 14
[ https://issues.apache.org/jira/browse/NIFI-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815417#comment-17815417 ] ASF subversion and git services commented on NIFI-12752: Commit 202ca3c638a5eaf986c9b74994c93a15fbac9b35 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=202ca3c638 ] NIFI-12752 Updated GitHub Workflows to use macos-14 - Upgraded setup-java action from v3 to v4 - Upgraded setup-python action from v4 to v5 - Updated system-tests to use Python 3.10 instead of Python 3.9 This closes #8371 Signed-off-by: David Handermann Signed-off-by: Joe Witt > Update GitHub Workflows using macOS 14 > --- > > Key: NIFI-12752 > URL: https://issues.apache.org/jira/browse/NIFI-12752 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > GitHub recently [released macOS > 14|https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/] > as a build platform for GitHub Actions. > The macOS 14 runner uses the Apple Silicon M1 Processor. This has the > advantage of testing build behavior on the AArch64 platform, which includes > performance benefits in some cases. > The ci-workflow and system-tests build configurations should be updated to > use macOS 14 to provide regular evaluation of behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12752 Update GitHub Workflows to use macos-14 [nifi]
exceptionfactory closed pull request #8371: NIFI-12752 Update GitHub Workflows to use macos-14 URL: https://github.com/apache/nifi/pull/8371 -- 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-12753 updating various github actions versions [nifi]
joewitt commented on PR #8373: URL: https://github.com/apache/nifi/pull/8373#issuecomment-1932768646 Actually the build passes for all areas but we do see in the codecov step of the ci-workflow Error: Codecov token not found. Please provide Codecov token with -t flag. Warning: Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1 -- 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-12753 updating various github actions versions [nifi]
joewitt opened a new pull request, #8373: URL: https://github.com/apache/nifi/pull/8373 # Summary [NIFI-12753](https://issues.apache.org/jira/browse/NIFI-12753) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 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-12751 [MiNiFi] Prefer IPv4 address when sending NetworkInfo to C2 [nifi]
briansolo1985 commented on code in PR #8370:
URL: https://github.com/apache/nifi/pull/8370#discussion_r1481938368
##
c2/c2-client-bundle/c2-client-service/src/main/java/org/apache/nifi/c2/client/service/C2HeartbeatFactory.java:
##
@@ -169,14 +171,20 @@ private NetworkInfo generateNetworkInfo() {
logger.debug("Instance has multiple interfaces. Generated
information may be non-deterministic.");
}
+boolean networkInfoUnset = true;
for (NetworkInterface networkInterface : operationIfaces) {
Enumeration inetAddresses =
networkInterface.getInetAddresses();
-if (inetAddresses.hasMoreElements()) {
+while (inetAddresses.hasMoreElements()) {
InetAddress inetAddress = inetAddresses.nextElement();
-networkInfo.setDeviceId(networkInterface.getName());
-networkInfo.setHostname(inetAddress.getHostName());
-networkInfo.setIpAddress(inetAddress.getHostAddress());
-break;
+// IPv4 address is preferred over IPv6 as it provides
more readable information for the user
+if (inetAddress instanceof Inet4Address) {
+updateNetworkInfo(networkInfo, networkInterface,
inetAddress);
+break;
+}
+if (networkInfoUnset) {
+updateNetworkInfo(networkInfo, networkInterface,
inetAddress);
+networkInfoUnset = false;
+}
Review Comment:
Thanks for the comment, good point. Made a change.
--
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 ] 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) ** 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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Status History - node specific values * Flow Configuration History * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies * 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) * Flow Analysis report menu [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) ***
[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) ** 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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * 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) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * More Details (Processor, Controller Service, Reporting Task) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * RPG Refresh * Color * Move to Front * Copy/Paste * Add/Update Info Icons in dialogs throughout the application * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies * 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) * Flow Analysis report menu [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
[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) ** 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 (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * 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) ** Overridden policy Empty or Copy (NIFI-12679) * 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 Component Version * Consider PG permissions in Toolbox (NIFI-12683) * 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 ** Disable and Configure * 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 (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * 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 * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Use polling interval from API * Routing error handling * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer ** Parameter Contexts ** Provenance ** Queue Listing (NIFI-12742) ** Summary (NIFI-12742) ** Users (NIFI-12742) ** Policies * 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) * Flow Analysis report menu [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) *
[jira] [Resolved] (NIFI-12687) BUG - y axis is missing from status history charts
[ https://issues.apache.org/jira/browse/NIFI-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan resolved NIFI-12687. Resolution: Fixed Fixed by https://github.com/apache/nifi/commit/c6f1d771e8 > BUG - y axis is missing from status history charts > -- > > Key: NIFI-12687 > URL: https://issues.apache.org/jira/browse/NIFI-12687 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > > NiFi 1.x: > !https://private-user-images.githubusercontent.com/713866/300824635-c3dd91cd-d1e3-4435-a061-c942d908db97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0NjM1LWMzZGQ5MWNkLWQxZTMtNDQzNS1hMDYxLWM5NDJkOTA4ZGI5Ny5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03YjlmMTg3YmUyN2Q1NWZkMWQ4ZDk4OGYxZjAxZjA1Mjc1MTc3MzI4M2Y0ZTczZGEyNzk3NTYwODFjZmQ4YjAxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.3ugCkPl9mECLrZIG55Fla6ndlOzMKxq098dKqUIv-bw! > > New UI: > !https://private-user-images.githubusercontent.com/713866/300824398-05fd832e-5051-458c-b0b5-0149dd203944.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0Mzk4LTA1ZmQ4MzJlLTUwNTEtNDU4Yy1iMGI1LTAxNDlkZDIwMzk0NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MmJhZDVlNDA3NzM5NjZmZGJkNzMzMDAzNWNhMmIwZjQ4OGJiZDk3YzU0MTgzMWI0ZjA2MDc1NWFlODcyMjk3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.sweJ-smR0nptjUc0dOJkEqlP975WFrPAhVE9M2BxGYQ! > > Discussion: https://github.com/apache/nifi/pull/8294#discussion_r1471227264 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12748) BUG - snackbar action button text in light mode is too dark
[ https://issues.apache.org/jira/browse/NIFI-12748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12748: --- Status: Patch Available (was: In Progress) > BUG - snackbar action button text in light mode is too dark > --- > > Key: NIFI-12748 > URL: https://issues.apache.org/jira/browse/NIFI-12748 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Attachments: Screenshot 2024-02-06 at 4.02.36 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > !Screenshot 2024-02-06 at 4.02.36 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12746) BUG - Search closes when user attempts to put focus back in search box
[ https://issues.apache.org/jira/browse/NIFI-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12746: --- Status: Patch Available (was: In Progress) > BUG - Search closes when user attempts to put focus back in search box > -- > > Key: NIFI-12746 > URL: https://issues.apache.org/jira/browse/NIFI-12746 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Scott Aslan >Priority: Major > Attachments: Kapture 2024-02-06 at 10.29.59.gif > > Time Spent: 10m > Remaining Estimate: 0h > > If you search for something, then select a result, then attempt to place the > focus back in the search box to modify the search term, it closes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12746) BUG - Search closes when user attempts to put focus back in search box
[ https://issues.apache.org/jira/browse/NIFI-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan reassigned NIFI-12746: -- Assignee: Scott Aslan > BUG - Search closes when user attempts to put focus back in search box > -- > > Key: NIFI-12746 > URL: https://issues.apache.org/jira/browse/NIFI-12746 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Scott Aslan >Priority: Major > Attachments: Kapture 2024-02-06 at 10.29.59.gif > > > If you search for something, then select a result, then attempt to place the > focus back in the search box to modify the search term, it closes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12753) Update various Github Actions versions for Github CI
[ https://issues.apache.org/jira/browse/NIFI-12753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815375#comment-17815375 ] Joe Witt commented on NIFI-12753: - https://github.com/apache/nifi/actions/runs/7817671166 > Update various Github Actions versions for Github CI > > > Key: NIFI-12753 > URL: https://issues.apache.org/jira/browse/NIFI-12753 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > > Shows some deprecation warnings related to github actions. We need to update > our workflows to use latest action versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12753) Update various Github Actions versions for Github CI
Joe Witt created NIFI-12753: --- Summary: Update various Github Actions versions for Github CI Key: NIFI-12753 URL: https://issues.apache.org/jira/browse/NIFI-12753 Project: Apache NiFi Issue Type: Improvement Reporter: Joe Witt Assignee: Joe Witt Shows some deprecation warnings related to github actions. We need to update our workflows to use latest action versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12734) Import from Registry
[ https://issues.apache.org/jira/browse/NIFI-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-12734: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Import from Registry > > > Key: NIFI-12734 > URL: https://issues.apache.org/jira/browse/NIFI-12734 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 3h > Remaining Estimate: 0h > > Add support to import a flow from the registry. This includes both the new > Process Group dialog and a new draggable icon in the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12734) Import from Registry
[ https://issues.apache.org/jira/browse/NIFI-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815368#comment-17815368 ] ASF subversion and git services commented on NIFI-12734: Commit 7ec2dd07c9d3fe7ca2239c4d0950fa81e825c136 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7ec2dd07c9 ] NIFI-12734: Import from Registry (#8354) * NIFI-12734: - Import from Registry. * NIFI-12734: - Providing better guidance when there are no registry clients available based on user permissions. - Showing form validation errors when there are no buckets or no flows. This closes #8354 > Import from Registry > > > Key: NIFI-12734 > URL: https://issues.apache.org/jira/browse/NIFI-12734 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 3h > Remaining Estimate: 0h > > Add support to import a flow from the registry. This includes both the new > Process Group dialog and a new draggable icon in the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12734: Import from Registry [nifi]
scottyaslan merged PR #8354: URL: https://github.com/apache/nifi/pull/8354 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-12708) UnpackContent should allow the user to specify a character set to apply in reading paths and filenames
[ https://issues.apache.org/jira/browse/NIFI-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt resolved NIFI-12708. - Resolution: Fixed > UnpackContent should allow the user to specify a character set to apply in > reading paths and filenames > -- > > Key: NIFI-12708 > URL: https://issues.apache.org/jira/browse/NIFI-12708 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Umar Hussain >Priority: Major > Fix For: 2.0.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > https://apachenifi.slack.com/archives/C0L9VCD47/p1706716977280569 > Timon Faerber > 1 hour ago > I am currently struggling with an encoding problem for unzipped files. > The following: > I have a .zip in my content, which Im not aware of how it was created (dont > know Character Set). > Then I use UnpackContent processor. > The path (folder) and filename is after that for unpacked files not encoded > in UTF-8 and the characters are output as ?. > I have already tried this solutions like > https://community.cloudera.com/t5/Support-Questions/Unable-to-write-a-file-with-Chinese-Characters-filename-in/m-p/177183, > for example, but it does not work for me. > Does anyone know another solution? > Joe Witt > 43 minutes ago > If you take nifi out of the equation and just unpack the zip using a command > line tool - does it see the paths/names correctly? > Joe Witt > 43 minutes ago > is there a sample zip you can share which has this problem? > Umar Hussain > 9 minutes ago > We tried it with unzip on Linux and if we give parameter -O Cp347 the German > characters ü ä ö in the path appear correctly in output. > But a simple unzip command also doesn't produce correct paths in output. > Joe Witt > 5 minutes ago > Interesting. So if you tell the zip program the encoding is cp347 the output > appears correct. otherwise it is incorrect yes? > New > Umar Hussain > 3 minutes ago > Yes, I think its the encoding of zip and the zip was created on a windows > machine and on Linux it's by default a different one. > The processor current implementation takes the platforms default encoding > Joe Witt > 3 minutes ago > Yeah this is probably a good summary of behavior we need to consider. > https://stackoverflow.com/questions/13261347/correctly-decoding-zip-entry-file-names-cp437-utf-8-or > Stack OverflowStack Overflow > Correctly decoding zip entry file names -- CP437, UTF-8 or? > I recently wrote a zip file I/O library called zipzap, but I'm struggling > with correctly decoding zip entry file names from arbitrary zip files. > Now, the PKWARE spec states: > D.1 The ZIP format ... > Joe Witt > 2 minutes ago > My guess is we need to allow the user to override the default behavior by > selecting the character set we'll read the filenames/paths as in some cases > of reading legacy app created zips -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12708) UnpackContent should allow the user to specify a character set to apply in reading paths and filenames
[ https://issues.apache.org/jira/browse/NIFI-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-12708: Fix Version/s: 2.0.0 > UnpackContent should allow the user to specify a character set to apply in > reading paths and filenames > -- > > Key: NIFI-12708 > URL: https://issues.apache.org/jira/browse/NIFI-12708 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Umar Hussain >Priority: Major > Fix For: 2.0.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > https://apachenifi.slack.com/archives/C0L9VCD47/p1706716977280569 > Timon Faerber > 1 hour ago > I am currently struggling with an encoding problem for unzipped files. > The following: > I have a .zip in my content, which Im not aware of how it was created (dont > know Character Set). > Then I use UnpackContent processor. > The path (folder) and filename is after that for unpacked files not encoded > in UTF-8 and the characters are output as ?. > I have already tried this solutions like > https://community.cloudera.com/t5/Support-Questions/Unable-to-write-a-file-with-Chinese-Characters-filename-in/m-p/177183, > for example, but it does not work for me. > Does anyone know another solution? > Joe Witt > 43 minutes ago > If you take nifi out of the equation and just unpack the zip using a command > line tool - does it see the paths/names correctly? > Joe Witt > 43 minutes ago > is there a sample zip you can share which has this problem? > Umar Hussain > 9 minutes ago > We tried it with unzip on Linux and if we give parameter -O Cp347 the German > characters ü ä ö in the path appear correctly in output. > But a simple unzip command also doesn't produce correct paths in output. > Joe Witt > 5 minutes ago > Interesting. So if you tell the zip program the encoding is cp347 the output > appears correct. otherwise it is incorrect yes? > New > Umar Hussain > 3 minutes ago > Yes, I think its the encoding of zip and the zip was created on a windows > machine and on Linux it's by default a different one. > The processor current implementation takes the platforms default encoding > Joe Witt > 3 minutes ago > Yeah this is probably a good summary of behavior we need to consider. > https://stackoverflow.com/questions/13261347/correctly-decoding-zip-entry-file-names-cp437-utf-8-or > Stack OverflowStack Overflow > Correctly decoding zip entry file names -- CP437, UTF-8 or? > I recently wrote a zip file I/O library called zipzap, but I'm struggling > with correctly decoding zip entry file names from arbitrary zip files. > Now, the PKWARE spec states: > D.1 The ZIP format ... > Joe Witt > 2 minutes ago > My guess is we need to allow the user to override the default behavior by > selecting the character set we'll read the filenames/paths as in some cases > of reading legacy app created zips -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12708 UnpackContent should allow the user to specify a character set to apply in reading paths and filenames [nifi]
joewitt commented on PR #8350: URL: https://github.com/apache/nifi/pull/8350#issuecomment-1932485274 Thanks @umarhussain15 - good work and good discussion -- 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-12708 UnpackContent should allow the user to specify a character set to apply in reading paths and filenames [nifi]
asfgit closed pull request #8350: NIFI-12708 UnpackContent should allow the user to specify a character set to apply in reading paths and filenames URL: https://github.com/apache/nifi/pull/8350 -- 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-12708) UnpackContent should allow the user to specify a character set to apply in reading paths and filenames
[ https://issues.apache.org/jira/browse/NIFI-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815364#comment-17815364 ] ASF subversion and git services commented on NIFI-12708: Commit e00d2b6d5e5ef7ffb726251b7edf94d0735ce7a8 in nifi's branch refs/heads/main from Umar Hussain [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e00d2b6d5e ] NIFI-12708: add option in UnpackContent to specify encoding charset for filenames in zip unpacking This closes #8350 The processor can now take a filename encoding parameter and pass it to zip unpacking. This will allow user to unzip files with specific encoding to get correct filenames in output. This for example help with zip files created on Windows which by default uses Cp437 for filename encoding. If the filename contains special character like German alphabet ä, ü etc., decoding this with Linux's default encoding usually UTF8 output will contain `?` in it. When the same file is processed with property set with `Cp437`, the processor outputs correct filenames with special characters preserved. Signed-off-by: Joseph Witt > UnpackContent should allow the user to specify a character set to apply in > reading paths and filenames > -- > > Key: NIFI-12708 > URL: https://issues.apache.org/jira/browse/NIFI-12708 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Umar Hussain >Priority: Major > Time Spent: 3h 10m > Remaining Estimate: 0h > > https://apachenifi.slack.com/archives/C0L9VCD47/p1706716977280569 > Timon Faerber > 1 hour ago > I am currently struggling with an encoding problem for unzipped files. > The following: > I have a .zip in my content, which Im not aware of how it was created (dont > know Character Set). > Then I use UnpackContent processor. > The path (folder) and filename is after that for unpacked files not encoded > in UTF-8 and the characters are output as ?. > I have already tried this solutions like > https://community.cloudera.com/t5/Support-Questions/Unable-to-write-a-file-with-Chinese-Characters-filename-in/m-p/177183, > for example, but it does not work for me. > Does anyone know another solution? > Joe Witt > 43 minutes ago > If you take nifi out of the equation and just unpack the zip using a command > line tool - does it see the paths/names correctly? > Joe Witt > 43 minutes ago > is there a sample zip you can share which has this problem? > Umar Hussain > 9 minutes ago > We tried it with unzip on Linux and if we give parameter -O Cp347 the German > characters ü ä ö in the path appear correctly in output. > But a simple unzip command also doesn't produce correct paths in output. > Joe Witt > 5 minutes ago > Interesting. So if you tell the zip program the encoding is cp347 the output > appears correct. otherwise it is incorrect yes? > New > Umar Hussain > 3 minutes ago > Yes, I think its the encoding of zip and the zip was created on a windows > machine and on Linux it's by default a different one. > The processor current implementation takes the platforms default encoding > Joe Witt > 3 minutes ago > Yeah this is probably a good summary of behavior we need to consider. > https://stackoverflow.com/questions/13261347/correctly-decoding-zip-entry-file-names-cp437-utf-8-or > Stack OverflowStack Overflow > Correctly decoding zip entry file names -- CP437, UTF-8 or? > I recently wrote a zip file I/O library called zipzap, but I'm struggling > with correctly decoding zip entry file names from arbitrary zip files. > Now, the PKWARE spec states: > D.1 The ZIP format ... > Joe Witt > 2 minutes ago > My guess is we need to allow the user to override the default behavior by > selecting the character set we'll read the filenames/paths as in some cases > of reading legacy app created zips -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12752 Update GitHub Workflows to use macos-14 [nifi]
joewitt commented on PR #8371: URL: https://github.com/apache/nifi/pull/8371#issuecomment-1932412323 @exceptionfactory wonderful find - +1 if the checks are green. please self merge! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12752) Update GitHub Workflows using macOS 14
[ https://issues.apache.org/jira/browse/NIFI-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12752: Status: Patch Available (was: Open) > Update GitHub Workflows using macOS 14 > --- > > Key: NIFI-12752 > URL: https://issues.apache.org/jira/browse/NIFI-12752 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > GitHub recently [released macOS > 14|https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/] > as a build platform for GitHub Actions. > The macOS 14 runner uses the Apple Silicon M1 Processor. This has the > advantage of testing build behavior on the AArch64 platform, which includes > performance benefits in some cases. > The ci-workflow and system-tests build configurations should be updated to > use macOS 14 to provide regular evaluation of behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12752 Update GitHub Workflows to use macos-14 [nifi]
exceptionfactory opened a new pull request, #8371: URL: https://github.com/apache/nifi/pull/8371 # Summary [NIFI-12752](https://issues.apache.org/jira/browse/NIFI-12752) Updates GitHub `ci-workflow` and `system-tests` automated builds to use `macos-14` for the macOS Runner. The [macos-14](https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/) version provides Apple Silicon M1 processing with the AArch64 architecture. This provides additional differentiation from the Ubuntu Linux and Windows builds, and also exhibits performance improvements over the current macOS runners. Additional changes include updating the `setup-java` action to version 4 and updating the `setup-python` action to version 5, with Python 3.10 for compatibility with macOS AArch64. # 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-12751 [MiNiFi] Prefer IPv4 address when sending NetworkInfo to C2 [nifi]
ferencerdei commented on code in PR #8370:
URL: https://github.com/apache/nifi/pull/8370#discussion_r1481696475
##
c2/c2-client-bundle/c2-client-service/src/main/java/org/apache/nifi/c2/client/service/C2HeartbeatFactory.java:
##
@@ -169,14 +171,20 @@ private NetworkInfo generateNetworkInfo() {
logger.debug("Instance has multiple interfaces. Generated
information may be non-deterministic.");
}
+boolean networkInfoUnset = true;
for (NetworkInterface networkInterface : operationIfaces) {
Enumeration inetAddresses =
networkInterface.getInetAddresses();
-if (inetAddresses.hasMoreElements()) {
+while (inetAddresses.hasMoreElements()) {
InetAddress inetAddress = inetAddresses.nextElement();
-networkInfo.setDeviceId(networkInterface.getName());
-networkInfo.setHostname(inetAddress.getHostName());
-networkInfo.setIpAddress(inetAddress.getHostAddress());
-break;
+// IPv4 address is preferred over IPv6 as it provides
more readable information for the user
+if (inetAddress instanceof Inet4Address) {
+updateNetworkInfo(networkInfo, networkInterface,
inetAddress);
+break;
+}
+if (networkInfoUnset) {
+updateNetworkInfo(networkInfo, networkInterface,
inetAddress);
+networkInfoUnset = false;
+}
Review Comment:
I think we should break the outer loop if any of these elements are found.
Now the last networkInterface data is used instead of the first
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (MINIFICPP-2259) ProcessContext::getProperty should operate on raw pointers
[ https://issues.apache.org/jira/browse/MINIFICPP-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marton Szasz updated MINIFICPP-2259: Resolution: Done Status: Resolved (was: Patch Available) > ProcessContext::getProperty should operate on raw pointers > -- > > Key: MINIFICPP-2259 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2259 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINIFICPP-2259) ProcessContext::getProperty should operate on raw pointers
[ https://issues.apache.org/jira/browse/MINIFICPP-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marton Szasz updated MINIFICPP-2259: Fix Version/s: 0.16.0 > ProcessContext::getProperty should operate on raw pointers > -- > > Key: MINIFICPP-2259 > URL: https://issues.apache.org/jira/browse/MINIFICPP-2259 > Project: Apache NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Martin Zink >Assignee: Martin Zink >Priority: Major > Fix For: 0.16.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] MINIFICPP-2259 ProcessContext::getProperty should operate on raw poin… [nifi-minifi-cpp]
szaszm closed pull request #1707: MINIFICPP-2259 ProcessContext::getProperty should operate on raw poin… URL: https://github.com/apache/nifi-minifi-cpp/pull/1707 -- 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-12751 [MiNiFi] Prefer IPv4 address when sending NetworkInfo to C2 [nifi]
briansolo1985 opened a new pull request, #8370: URL: https://github.com/apache/nifi/pull/8370 # Summary [NIFI-12751](https://issues.apache.org/jira/browse/NIFI-12751) # 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-12745) AvroReader silently drops record if it's malformed
[
https://issues.apache.org/jira/browse/NIFI-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajmund Takacs updated NIFI-12745:
--
Attachment: ValidateRecord.json
> AvroReader silently drops record if it's malformed
> --
>
> Key: NIFI-12745
> URL: https://issues.apache.org/jira/browse/NIFI-12745
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 2.0.0-M1, 1.18.0, 1.19.0, 1.20.0, 1.19.1, 1.21.0,
> 1.22.0, 1.23.0, 1.24.0, 1.23.1, 1.23.2, 1.25.0, 2.0.0-M2
>Reporter: Rajmund Takacs
>Assignee: Rajmund Takacs
>Priority: Major
> Attachments: ValidateRecord.json
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See the attached example flow. It reproduces the issue very reliably.
> {{GenerateFlowFile}} is set to generate the following Json:
> {code:json}
> [{
> "field_1" : 123456789,
> "field_2" : "44",
> "field_3" : 5
> }]
> {code}
> This input is converted to Avro format, using the {{ConvertRecord}}
> processor. The 'Schema Write Strategy' of {{AvroRecordSetWriter}} is set to
> anything different than 'Embed Avro Schema'.
> Then, the resulting FF is routed to a processor that uses an {{AvroReader}}
> to work on the records. The reader is set to use a predefined, fixed schema,
> which does not match with the input avro file, contains at least an extra
> field. It does not matter if that field has a default value or not.
> {code:json}
> {
> "type":"record",
> "name":"message_name",
> "namespace":"message_namespace",
> "fields":[
> {
> "name":"field_1",
> "type":["long"]
> },
> {
> "name":"field_2",
> "type":["string"]
> },
> {
> "name":"field_3",
> "type":["int"]
> },
> {
> "name":"extra_field",
> "type":["string"],
> "default":"empty"
> }
> ]
> }
> {code}
> When this processor consumes the input, the reader silently drops the record,
> without even making an error log message. At the processor level, this is
> equivalent to having no records to process, so nothing happens. The user
> won't notice that there is a misconfiguration somewhere until they start
> noticing the missing the flow files.
> The expected behavior from the processors would be to route the malformed
> input FF to their failure relationship, and shout an error on its bulletin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12745) AvroReader silently drops record if it's malformed
[
https://issues.apache.org/jira/browse/NIFI-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajmund Takacs updated NIFI-12745:
--
Attachment: (was: engesc_ValidateRecord_1.18.0.NiFi_Flow.json)
> AvroReader silently drops record if it's malformed
> --
>
> Key: NIFI-12745
> URL: https://issues.apache.org/jira/browse/NIFI-12745
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 2.0.0-M1, 1.18.0, 1.19.0, 1.20.0, 1.19.1, 1.21.0,
> 1.22.0, 1.23.0, 1.24.0, 1.23.1, 1.23.2, 1.25.0, 2.0.0-M2
>Reporter: Rajmund Takacs
>Assignee: Rajmund Takacs
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See the attached example flow. It reproduces the issue very reliably.
> {{GenerateFlowFile}} is set to generate the following Json:
> {code:json}
> [{
> "field_1" : 123456789,
> "field_2" : "44",
> "field_3" : 5
> }]
> {code}
> This input is converted to Avro format, using the {{ConvertRecord}}
> processor. The 'Schema Write Strategy' of {{AvroRecordSetWriter}} is set to
> anything different than 'Embed Avro Schema'.
> Then, the resulting FF is routed to a processor that uses an {{AvroReader}}
> to work on the records. The reader is set to use a predefined, fixed schema,
> which does not match with the input avro file, contains at least an extra
> field. It does not matter if that field has a default value or not.
> {code:json}
> {
> "type":"record",
> "name":"message_name",
> "namespace":"message_namespace",
> "fields":[
> {
> "name":"field_1",
> "type":["long"]
> },
> {
> "name":"field_2",
> "type":["string"]
> },
> {
> "name":"field_3",
> "type":["int"]
> },
> {
> "name":"extra_field",
> "type":["string"],
> "default":"empty"
> }
> ]
> }
> {code}
> When this processor consumes the input, the reader silently drops the record,
> without even making an error log message. At the processor level, this is
> equivalent to having no records to process, so nothing happens. The user
> won't notice that there is a misconfiguration somewhere until they start
> noticing the missing the flow files.
> The expected behavior from the processors would be to route the malformed
> input FF to their failure relationship, and shout an error on its bulletin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12752) Update GitHub Workflows using macOS 14
David Handermann created NIFI-12752: --- Summary: Update GitHub Workflows using macOS 14 Key: NIFI-12752 URL: https://issues.apache.org/jira/browse/NIFI-12752 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: David Handermann Assignee: David Handermann GitHub recently [released macOS 14|https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/] as a build platform for GitHub Actions. The macOS 14 runner uses the Apple Silicon M1 Processor. This has the advantage of testing build behavior on the AArch64 platform, which includes performance benefits in some cases. The ci-workflow and system-tests build configurations should be updated to use macOS 14 to provide regular evaluation of behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINIFICPP-2298) Set RocksDB keep_log_file_num to something reasonable, like 5, from the default 1000
Marton Szasz created MINIFICPP-2298: --- Summary: Set RocksDB keep_log_file_num to something reasonable, like 5, from the default 1000 Key: MINIFICPP-2298 URL: https://issues.apache.org/jira/browse/MINIFICPP-2298 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Marton Szasz RocksDB keeps many old logs, which can have a significant size. We should only keep the 5-10 most recent ones for debugging purposes, and delete the rest, so they don't take up gigabytes of space in user environments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12751) [MiNiFi] Prefer IPv4 address for creating NetworkInfo
Ferenc Kis created NIFI-12751:
-
Summary: [MiNiFi] Prefer IPv4 address for creating NetworkInfo
Key: NIFI-12751
URL: https://issues.apache.org/jira/browse/NIFI-12751
Project: Apache NiFi
Issue Type: Improvement
Components: MiNiFi
Reporter: Ferenc Kis
Assignee: Ferenc Kis
On Windows Server 2019 the agent sends the following
{code}
"networkInfo": \{
"deviceId": "ethernet_32777",
"hostname": "fe80:0:0:0:6f46:95b8:1b4d:9ab5%ethernet_32777",
"ipAddress": "fe80:0:0:0:6f46:95b8:1b4d:9ab5%ethernet_32777"
},
{code}
The same network interface also has an IPv4 address where the hostname matches
what the hostname command would give back in the shell.
In such cases when the same network interface has IPv4 and IPv6 addresses,
prefer the the IPv4 as it provides more information for the user.
Note: this does not affect anything in terms of network connectivity, only the
information which is sent by the agent to the C2 server
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [NIFI-12665] fetch parameter provider parameters [nifi]
rfellows commented on code in PR #8367:
URL: https://github.com/apache/nifi/pull/8367#discussion_r1481600645
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/settings/state/parameter-providers/parameter-providers.effects.ts:
##
@@ -61,9 +71,17 @@ export class ParameterProvidersEffects {
}
})
),
-catchError((error) =>
-
of(ParameterProviderActions.parameterProvidersApiError({ error: error.error }))
-)
+catchError((error: HttpErrorResponse) => {
+if (status === 'success') {
Review Comment:
good catch. i think i write this before that was available.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [NIFI-12665] fetch parameter provider parameters [nifi]
mcgilman commented on code in PR #8367:
URL: https://github.com/apache/nifi/pull/8367#discussion_r1481486857
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/settings/state/parameter-providers/parameter-providers.effects.ts:
##
@@ -61,9 +71,17 @@ export class ParameterProvidersEffects {
}
})
),
-catchError((error) =>
-
of(ParameterProviderActions.parameterProvidersApiError({ error: error.error }))
-)
+catchError((error: HttpErrorResponse) => {
+if (status === 'success') {
Review Comment:
`ErrorHelper.handleLoadingError` can be used here.
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/settings/state/parameter-providers/parameter-providers.actions.ts:
##
@@ -24,9 +24,14 @@ import {
DeleteParameterProviderRequest,
DeleteParameterProviderSuccess,
EditParameterProviderRequest,
+FetchParameterProviderParametersRequest,
+FetchParameterProviderParametersResponse,
LoadParameterProvidersResponse,
+ParameterProviderParameterApplicationEntity,
+PollParameterProviderParametersUpdateSuccess,
SelectParameterProviderRequest
} from './index';
+import { FetchParameterProviderParameters } from
'../../ui/parameter-providers/fetch-parameter-provider-parameters/fetch-parameter-provider-parameters.component';
Review Comment:
This is unused.
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/settings/ui/parameter-providers/fetch-parameter-provider-parameters/fetch-parameter-provider-parameters.component.ts:
##
@@ -0,0 +1,600 @@
+/*
+ * 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 { Component, Inject, Input, OnInit } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import { MAT_DIALOG_DATA, MatDialogModule } from '@angular/material/dialog';
+import { FormBuilder, FormControl, FormGroup, ReactiveFormsModule, Validators
} from '@angular/forms';
+import { ErrorBanner } from
'../../../../../ui/common/error-banner/error-banner.component';
+import { MatButtonModule } from '@angular/material/button';
+import { NifiSpinnerDirective } from
'../../../../../ui/common/spinner/nifi-spinner.directive';
+import { Client } from '../../../../../service/client.service';
+import { NiFiCommon } from '../../../../../service/nifi-common.service';
+import {
+FetchedParameterMapping,
+FetchParameterProviderDialogRequest,
+ParameterGroupConfiguration,
+ParameterProviderApplyParametersRequest,
+ParameterProviderEntity,
+ParameterProviderParameterApplicationEntity,
+ParameterProvidersState,
+ParameterSensitivity,
+ParameterStatusEntity
+} from '../../../state/parameter-providers';
+import { debounceTime, Observable, Subject } from 'rxjs';
+import { TextTip } from
'../../../../../ui/common/tooltips/text-tip/text-tip.component';
+import { NifiTooltipDirective } from
'../../../../../ui/common/tooltips/nifi-tooltip.directive';
+import { MatTableDataSource, MatTableModule } from '@angular/material/table';
+import { MatSortModule, Sort } from '@angular/material/sort';
+import { ParameterGroupsTable } from
'./parameter-groups-table/parameter-groups-table.component';
+import { MatCheckboxChange, MatCheckboxModule } from
'@angular/material/checkbox';
+import { MatInputModule } from '@angular/material/input';
+import { ParameterReferences } from
'../../../../../ui/common/parameter-references/parameter-references.component';
+import { AffectedComponentEntity } from '../../../../../state/shared';
+import * as ParameterProviderActions from
'../../../state/parameter-providers/parameter-providers.actions';
+import { Store } from '@ngrx/store';
+
+@Component({
+selector: 'fetch-parameter-provider-parameters',
+standalone: true,
+imports: [
+CommonModule,
+MatDialogModule,
+ReactiveFormsModule,
+ErrorBanner,
+
Re: [PR] NIFI-12236 Improving fault tolerancy of the QuestDB backed metrics repository [nifi]
simonbence commented on code in PR #8152:
URL: https://github.com/apache/nifi/pull/8152#discussion_r1481596508
##
nifi-nar-bundles/nifi-questdb-bundle/nifi-questdb/src/test/java/org/apache/nifi/questdb/embedded/EmbeddedDatabaseManagerTest.java:
##
@@ -0,0 +1,397 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.questdb.embedded;
+
+import org.apache.commons.lang3.SystemUtils;
+import org.apache.nifi.questdb.Client;
+import org.apache.nifi.questdb.DatabaseException;
+import org.apache.nifi.questdb.DatabaseManager;
+import org.apache.nifi.questdb.mapping.RequestMapping;
+import org.apache.nifi.questdb.rollover.RolloverStrategy;
+import org.apache.nifi.questdb.util.Event;
+import org.apache.nifi.questdb.util.QuestDbTestUtil;
+import org.apache.nifi.util.file.FileUtils;
+import org.junit.jupiter.api.Disabled;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.Timeout;
+import org.junit.jupiter.api.condition.DisabledOnOs;
+import org.junit.jupiter.api.condition.OS;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.BufferedWriter;
+import java.io.File;
+import java.io.FileWriter;
+import java.io.IOException;
+import java.time.Instant;
+import java.time.temporal.ChronoUnit;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicReference;
+import java.util.stream.StreamSupport;
+
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT2_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT2_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.SELECT_QUERY;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getRandomTestData;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getTestData;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertIterableEquals;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+public class EmbeddedDatabaseManagerTest extends EmbeddedQuestDbTest {
+private static final Logger LOGGER =
LoggerFactory.getLogger(EmbeddedDatabaseManagerTest.class);
+private static final int DAYS_TO_KEEP_EVENT = 1;
+private static final String NON_EXISTING_PLACE = SystemUtils.IS_OS_WINDOWS
? "T:/nonExistingPlace" : "/nonExistingPlace";
+
+@Test
+public void testAcquiringWithoutInitialization() {
+final EmbeddedDatabaseManager testSubject = new
EmbeddedDatabaseManager(new SimpleEmbeddedDatabaseManagerContext());
+assertThrows(IllegalStateException.class, () ->
testSubject.acquireClient());
+}
+
+@Test
+public void testHappyPath() throws DatabaseException {
+final List testData = getTestData();
+final DatabaseManager testSubject = getTestSubject();
+assertDatabaseFolderIsNotEmpty();
+
+final Client client = testSubject.acquireClient();
+
+client.insert(EVENT_TABLE_NAME,
QuestDbTestUtil.getEventTableDataSource(testData));
+final List result = client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING));
+
+assertIterableEquals(testData, result);
+
+testSubject.close();
+
+// Even if the client itself is not connected, manager prevents client
to reach database after closing
+assertFalse(client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING)).iterator().hasNext());
+}
+
+@Test
+public void testRollover() throws DatabaseException, InterruptedException {
+final List testData = new ArrayList<>();
+testData.add(new Event(Instant.now().minus((DAYS_TO_KEEP_EVENT + 1),
ChronoUnit.DAYS), "A", 1));
+testData.add(new Event(Instant.now(), "B", 2));
+
Re: [PR] NIFI-12236 Improving fault tolerancy of the QuestDB backed metrics repository [nifi]
simonbence commented on code in PR #8152:
URL: https://github.com/apache/nifi/pull/8152#discussion_r1481594813
##
nifi-nar-bundles/nifi-questdb-bundle/nifi-questdb/src/test/java/org/apache/nifi/questdb/embedded/EmbeddedDatabaseManagerTest.java:
##
@@ -0,0 +1,397 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.questdb.embedded;
+
+import org.apache.commons.lang3.SystemUtils;
+import org.apache.nifi.questdb.Client;
+import org.apache.nifi.questdb.DatabaseException;
+import org.apache.nifi.questdb.DatabaseManager;
+import org.apache.nifi.questdb.mapping.RequestMapping;
+import org.apache.nifi.questdb.rollover.RolloverStrategy;
+import org.apache.nifi.questdb.util.Event;
+import org.apache.nifi.questdb.util.QuestDbTestUtil;
+import org.apache.nifi.util.file.FileUtils;
+import org.junit.jupiter.api.Disabled;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.Timeout;
+import org.junit.jupiter.api.condition.DisabledOnOs;
+import org.junit.jupiter.api.condition.OS;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.BufferedWriter;
+import java.io.File;
+import java.io.FileWriter;
+import java.io.IOException;
+import java.time.Instant;
+import java.time.temporal.ChronoUnit;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicReference;
+import java.util.stream.StreamSupport;
+
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT2_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.CREATE_EVENT_TABLE;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT2_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.EVENT_TABLE_NAME;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.SELECT_QUERY;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getRandomTestData;
+import static org.apache.nifi.questdb.util.QuestDbTestUtil.getTestData;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertIterableEquals;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+public class EmbeddedDatabaseManagerTest extends EmbeddedQuestDbTest {
+private static final Logger LOGGER =
LoggerFactory.getLogger(EmbeddedDatabaseManagerTest.class);
+private static final int DAYS_TO_KEEP_EVENT = 1;
+private static final String NON_EXISTING_PLACE = SystemUtils.IS_OS_WINDOWS
? "T:/nonExistingPlace" : "/nonExistingPlace";
+
+@Test
+public void testAcquiringWithoutInitialization() {
+final EmbeddedDatabaseManager testSubject = new
EmbeddedDatabaseManager(new SimpleEmbeddedDatabaseManagerContext());
+assertThrows(IllegalStateException.class, () ->
testSubject.acquireClient());
+}
+
+@Test
+public void testHappyPath() throws DatabaseException {
+final List testData = getTestData();
+final DatabaseManager testSubject = getTestSubject();
+assertDatabaseFolderIsNotEmpty();
+
+final Client client = testSubject.acquireClient();
+
+client.insert(EVENT_TABLE_NAME,
QuestDbTestUtil.getEventTableDataSource(testData));
+final List result = client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING));
+
+assertIterableEquals(testData, result);
+
+testSubject.close();
+
+// Even if the client itself is not connected, manager prevents client
to reach database after closing
+assertFalse(client.query(SELECT_QUERY,
RequestMapping.getResultProcessor(QuestDbTestUtil.EVENT_TABLE_REQUEST_MAPPING)).iterator().hasNext());
+}
+
+@Test
+public void testRollover() throws DatabaseException, InterruptedException {
+final List testData = new ArrayList<>();
+testData.add(new Event(Instant.now().minus((DAYS_TO_KEEP_EVENT + 1),
ChronoUnit.DAYS), "A", 1));
+testData.add(new Event(Instant.now(), "B", 2));
+
Re: [PR] [NIFI-12665] fetch parameter provider parameters [nifi]
rfellows commented on PR #8367: URL: https://github.com/apache/nifi/pull/8367#issuecomment-1932181773 recheck -- 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-12750) ExecuteStreamCommand incorrectly decodes error stream
René Zeidler created NIFI-12750:
---
Summary: ExecuteStreamCommand incorrectly decodes error stream
Key: NIFI-12750
URL: https://issues.apache.org/jira/browse/NIFI-12750
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 2.0.0-M2, 1.25.0
Environment: any
Reporter: René Zeidler
Attachments: ExecuteStreamCommand_Encoding_Bug.json, encodingTest.sh,
image-2024-02-07-15-14-08-518.png, image-2024-02-07-15-14-54-841.png,
image-2024-02-07-15-20-11-684.png
h1. Summary
The ExecuteStreamCommand processor stores everything the invoked command writes
to the error stream (stderr) into the FlowFile attribute
{{{}execution.error{}}}.
When converting the bytes from the stream to a String, it interprets each
individual byte as a Unicode codepoint. When reading only single bytes this
effectively results in ISO-8859-1 (Latin-1).
Instead, it should use the system default encoding (like it already does for
writing stdout if Output Destination Attribute is set) or use a configurable
encoding (for both stdout and stderr).
h1. Details
When reading/writing FlowFiles, NiFi always uses raw bytes, so encoding issues
are the responsibility of the flow designer, and NiFi has the
ConvertCharacterSet processor to deal with those issues.
When writing to attributes, the API uses Java String objects, which are
encoding agnostic (they represent Unicode codepoints, not bytes). Therefore,
processors receiving bytes have to interpret them using an encoding.
The ExecuteStreamCommand processor writes the output of the command (stdout) to
the Output Destination Attribute (if set). To do that, it convertes bytes into
a String using the system default encoding* by calling {{new String}} without
an encoding argument:
[https://github.com/apache/nifi/blob/72f6d8a6800c643d5f283ae9bff6d7de25b503e9/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteStreamCommand.java#L499]
When converting stderr to a String to write into the {{execution.error}}
attribute, it uses this weird algorithm:
[https://github.com/apache/nifi/blob/72f6d8a6800c643d5f283ae9bff6d7de25b503e9/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteStreamCommand.java#L507-L517]
It reads individual bytes from the error stream (as {{{}int{}}}s) and casts
them to {{{}char{}}}s. What Java does in this case is interpret the integer as
a Unicode code point. For single bytes, this matches the ISO-8859-1 encoding.
Instead, it should use the same decoding method as for stdout.
h1. Reproduction steps
These steps are for a Linux environment, but can be adapted with a different
executable for Windows.
# Create the file /opt/nifi/data/encodingTest.sh (attached) with the following
contents and make it executable:
{quote}{{#/bin/bash}}
{{echo "|out static: ÄÖÜäöüß"}}
{{{}echo "|error static: ÄÖÜäöüß" >&2{}}}{{{}echo "|out arg: $1"{}}}
{{{}echo "|error arg: $1" >&2{}}}{{{}echo "|out arg hexdump:"{}}}
{{printf '%s' "$1" | od -A x -t x1z -v}}
{{echo "|error arg hexdump:" >&2}}
{{printf '%s' "$1" | od -A x -t x1z -v >&2}}{quote}The script writes identical
data to both stdout and stderr. It contains non-ASCII characters to make the
encoding issues visible.
# Import the attached flow or create it manually:
!image-2024-02-07-15-14-08-518.png|width=324,height=373!!image-2024-02-07-15-14-54-841.png|width=326,height=120!
# Run the GenerateFlowFile processor once and observe the attributes of the
FlowFile in the final queue:
!image-2024-02-07-15-20-11-684.png|width=523,height=195!
The output attribute (stdout) is correctly decoded. The execution.error
attribute (stderr) contains garbled text (UTF-8 bytes interpreted as ISO-8859-1
and reencoded in UTF-8).
h1. *On the system default encoding
The system default encoding is a property of the JVM. It is UTF-8 on Linux, but
Windows-1252 (or a different copepage depending on locale) in Windows
environments. It can be overriden using the {{file.encoding}} JVM arg on
startup.
Relying on the system default encoding is dangerous and can lead to subtle
bugs, like the ones I previously reported (NIFI-12669 and NIFI-12670).
In this case, it might make sense to use the system default encoding, as it
concerns data passed between NiFi and another process that runs on the host
system. Also, the ProcessBuilder class used the create the process always
passes arguments in the system default encoding, and there doesn't seem a way
to change that. This behavior should probably be documented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MINIFICPP-2297) Remove iOS support from build system
Gábor Gyimesi created MINIFICPP-2297: Summary: Remove iOS support from build system Key: MINIFICPP-2297 URL: https://issues.apache.org/jira/browse/MINIFICPP-2297 Project: Apache NiFi MiNiFi C++ Issue Type: Improvement Reporter: Gábor Gyimesi Assignee: Gábor Gyimesi The project was not built for iOS for years and is not maintained at all, should be removed from the build options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] MINIFICPP-2276 Support FlowFileTransform NiFi Python processors [nifi-minifi-cpp]
adamdebreceni commented on code in PR #1712:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1712#discussion_r1481497293
##
extensions/python/PYTHON.md:
##
@@ -106,20 +127,39 @@ class VaderSentiment(object):
To enable python Processor capabilities, the following options need to be
provided in minifi.properties. The directory specified
can contain processors. Note that the processor name will be the reference in
your flow. Directories are treated like package names.
Therefore if the nifi.python.processor.dir is /tmp/ and you have a
subdirectory named packagedir with the file name file.py, it will
-produce a processor with the name
org.apache.nifi.minifi.processors.packagedir.file. Note that each subdirectory
will append a package
-to the reference class name.
+produce a processor with the name
org.apache.nifi.minifi.processors.packagedir.file. Note that each subdirectory
will append a package
+to the reference class name.
in minifi.properties
#directory where processors exist
nifi.python.processor.dir=
-
-
+
+
## Processors
The python directory (extensions/pythonprocessors) contains implementations
that will be available for flows if the required dependencies
exist.
-
-## Sentiment Analysis
+
+### Sentiment Analysis
The SentimentAnalysis processor will perform a Vader Sentiment Analysis. This
requires that you install nltk and VaderSentiment
pip install nltk
pip install VaderSentiment
+
+## Using NiFi Python Processors
+
+MiNiFi C++ supports the use of NiFi Python processors, that are inherited from
the FlowFileTransform base class. To use these processors, you must copy the
Python processor module under the nifi_python_processors directory located
under the python directory (by default it can be found at
${minifi_root}/minifi-python/nifi_python_processors). To see how to to write
NiFi Python processors, please refer to the Python Developer Guide under the
[Apache NiFi documentation](https://nifi.apache.org/documentation/v2/).
Review Comment:
"how to to write NiFi"
--
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-12665] fetch parameter provider parameters [nifi]
mcgilman commented on PR #8367: URL: https://github.com/apache/nifi/pull/8367#issuecomment-1932061106 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] [Commented] (NIFI-12727) Detect Dark mode from OS settings but also offer opt out
[ https://issues.apache.org/jira/browse/NIFI-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815304#comment-17815304 ] ASF subversion and git services commented on NIFI-12727: Commit f39f3ea2520d3b5e9d8c541dbb932329ecbabc4f in nifi's branch refs/heads/main from Scott Aslan [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f39f3ea252 ] [NIFI-12727] Detect theme based on OS setting, allow user override (#8352) * [NIFI-12727] Detect theme based on OS setting, allow user override * update storage service types, introduce theming service for user selection of theme settings * review feedback, update menu option disaplay names, update storage service types, delete expired local storage items on init * check for existence of window.matchmedia * rebase and address review comments This closes #8352 > Detect Dark mode from OS settings but also offer opt out > > > Key: NIFI-12727 > URL: https://issues.apache.org/jira/browse/NIFI-12727 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12727) Detect Dark mode from OS settings but also offer opt out
[ https://issues.apache.org/jira/browse/NIFI-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12727: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Detect Dark mode from OS settings but also offer opt out > > > Key: NIFI-12727 > URL: https://issues.apache.org/jira/browse/NIFI-12727 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12727] Detect theme based on OS setting, allow user override [nifi]
mcgilman merged PR #8352: URL: https://github.com/apache/nifi/pull/8352 -- 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-12749) NiFi Toolkit export-all-flows fails when flow name contains '/'
[ https://issues.apache.org/jira/browse/NIFI-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12749: --- Status: Patch Available (was: In Progress) > NiFi Toolkit export-all-flows fails when flow name contains '/' > --- > > Key: NIFI-12749 > URL: https://issues.apache.org/jira/browse/NIFI-12749 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The command fails if there are any flows in the registry that has a / > character because when exporting the flow, the toolkit assumes / is a path > separator as the toolkit will use the versioned flow name and version when > creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12749 NiFi Toolkit export-all-flows fails when flow name contain… [nifi]
timeabarna opened a new pull request, #8369: URL: https://github.com/apache/nifi/pull/8369 …s '/' # Summary The command fails if there are any flows in the registry that has a / character because when exporting the flow, the toolkit assumes / is a path separator as the toolkit will use the versioned flow name and version when creating the exported files. [NIFI-12749](https://issues.apache.org/jira/browse/NIFI-12749) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 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-12749) NiFi Toolkit export-all-flows fails when flow name contains '/'
[ https://issues.apache.org/jira/browse/NIFI-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timea Barna updated NIFI-12749: --- Summary: NiFi Toolkit export-all-flows fails when flow name contains '/' (was: NiFi Toolkit export-all-flows fails when flow name contains has '/') > NiFi Toolkit export-all-flows fails when flow name contains '/' > --- > > Key: NIFI-12749 > URL: https://issues.apache.org/jira/browse/NIFI-12749 > Project: Apache NiFi > Issue Type: Bug >Reporter: Timea Barna >Assignee: Timea Barna >Priority: Major > > The command fails if there are any flows in the registry that has a / > character because when exporting the flow, the toolkit assumes / is a path > separator as the toolkit will use the versioned flow name and version when > creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12749) NiFi Toolkit export-all-flows fails when flow name contains has '/'
Timea Barna created NIFI-12749: -- Summary: NiFi Toolkit export-all-flows fails when flow name contains has '/' Key: NIFI-12749 URL: https://issues.apache.org/jira/browse/NIFI-12749 Project: Apache NiFi Issue Type: Bug Reporter: Timea Barna Assignee: Timea Barna The command fails if there are any flows in the registry that has a / character because when exporting the flow, the toolkit assumes / is a path separator as the toolkit will use the versioned flow name and version when creating the exported files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12671) Implement AWS option for FileResourceService
[ https://issues.apache.org/jira/browse/NIFI-12671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Gerner updated NIFI-12671: - Status: Patch Available (was: In Progress) > Implement AWS option for FileResourceService > > > Key: NIFI-12671 > URL: https://issues.apache.org/jira/browse/NIFI-12671 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Balázs Gerner >Assignee: Balázs Gerner >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add S3 based implementation for the FileResourceService interface to be able > to fetch data directly from AWS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12671 Added AwsFileResourceService [nifi]
balazsgerner opened a new pull request, #8368: URL: https://github.com/apache/nifi/pull/8368 # Summary [NIFI-12671](https://issues.apache.org/jira/browse/NIFI-12671) Implemented the AWS S3 specific version of FileResourceService to be able to fetch data directly from this service, by-passing the content repository. # 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 - [x] 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] (MINIFICPP-2296) Install application as a service with minifi.sh install command
Adam Debreceni created MINIFICPP-2296: - Summary: Install application as a service with minifi.sh install command Key: MINIFICPP-2296 URL: https://issues.apache.org/jira/browse/MINIFICPP-2296 Project: Apache NiFi MiNiFi C++ Issue Type: New Feature Reporter: Adam Debreceni Assignee: Adam Debreceni -- This message was sent by Atlassian Jira (v8.20.10#820010)
