You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by ex...@apache.org on 2023/10/27 13:54:22 UTC

(nifi) branch support/nifi-1.x updated (67767b6550 -> b9a2371afe)

This is an automated email from the ASF dual-hosted git repository.

exceptionfactory pushed a change to branch support/nifi-1.x
in repository https://gitbox.apache.org/repos/asf/nifi.git


    from 67767b6550 NIFI-12130: Ability to configure snapshot properties via dynamic attributes in PutIceberg
     new b822c27fb5 NIFI-11677 Removed non required yield in DeleteHDFS
     new b9a2371afe NIFI-12273 Fixed command.argument references in ExecuteStreamCommand docs

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java   | 1 -
 .../additionalDetails.html                                        | 8 ++++----
 2 files changed, 4 insertions(+), 5 deletions(-)


(nifi) 01/02: NIFI-11677 Removed non required yield in DeleteHDFS

Posted by ex...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

exceptionfactory pushed a commit to branch support/nifi-1.x
in repository https://gitbox.apache.org/repos/asf/nifi.git

commit b822c27fb5bf409cd47157da40cd02588bdfcd53
Author: Pierre Villard <pi...@gmail.com>
AuthorDate: Thu Oct 26 12:13:06 2023 -0700

    NIFI-11677 Removed non required yield in DeleteHDFS
    
    This closes #7937
    
    Signed-off-by: David Handermann <ex...@apache.org>
    (cherry picked from commit 1d125e9906090eedb66a7f6f8f1176ac67e007bc)
---
 .../src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java      | 1 -
 1 file changed, 1 deletion(-)

diff --git a/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java b/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
index 7f9459f03f..b56f561d14 100644
--- a/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
+++ b/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
@@ -139,7 +139,6 @@ public class DeleteHDFS extends AbstractHadoopProcessor {
         // If this processor has an incoming connection, then do not run unless a
         // FlowFile is actually sent through
         if (originalFlowFile == null && context.hasIncomingConnection()) {
-            context.yield();
             return;
         }
 


(nifi) 02/02: NIFI-12273 Fixed command.argument references in ExecuteStreamCommand docs

Posted by ex...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

exceptionfactory pushed a commit to branch support/nifi-1.x
in repository https://gitbox.apache.org/repos/asf/nifi.git

commit b9a2371afe3e694acfff9ac07b0a2c563e92ebd7
Author: Matt Burgess <ma...@apache.org>
AuthorDate: Thu Oct 26 20:20:43 2023 -0400

    NIFI-12273 Fixed command.argument references in ExecuteStreamCommand docs
    
    This closes #7941
    
    Signed-off-by: David Handermann <ex...@apache.org>
    (cherry picked from commit 880770f992c9bf85629d90031024c3a60356ba2f)
---
 .../additionalDetails.html                                        | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html
index 23fd22f0da..c22d859744 100644
--- a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html
+++ b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/docs/org.apache.nifi.processors.standard.ExecuteStreamCommand/additionalDetails.html
@@ -53,7 +53,7 @@
         <p><b>NOTE:</b> the command should be on <code>$PATH</code> or it should be in the working directory, otherwise path also should be specified.</p>
 
         <h4>Dynamic Properties</h4>
-        <p>Arguments can be specified with Dynamic Properties. Dynamic Properties with the pattern of 'command.arguments.&lt;commandIndex&gt;' will be appended
+        <p>Arguments can be specified with Dynamic Properties. Dynamic Properties with the pattern of 'command.argument.&lt;commandIndex&gt;' will be appended
         to the command in ascending order.</p>
 
         <p>The above example with dynamic properties would look like this:</p>
@@ -64,11 +64,11 @@
                 <th>Property Value</th>
             </tr>
             <tr>
-                <td>command.arguments.0</td>
+                <td>command.argument.0</td>
                 <td>-lah</td>
             </tr>
             <tr>
-                <td>command.arguments.1</td>
+                <td>command.argument.1</td>
                 <td>/path/to/dir</td>
             </tr>
         </table>
@@ -76,7 +76,7 @@
         <h3>Configuring environment variables</h3>
         <p>In addition to specifying command arguments using the Command Argument field or Dynamic Properties, users can also use environment variables with
         the ExecuteStreamCommand processor. Environment variables are a set of key-value pairs that can be accessed by processes running on the system.
-        ExecuteStreamCommand will treat every Dynamic Property as an environment variable that doesn't match the pattern 'command.arguments.&lt;commandIndex&gt;'.</p>
+        ExecuteStreamCommand will treat every Dynamic Property as an environment variable that doesn't match the pattern 'command.argument.&lt;commandIndex&gt;'.</p>
 
         <p>Consider that we want to execute a Maven command with the processor. If there are multiple Java versions installed on the system, you can specify
         which version will be used by setting the <code>JAVA_HOME</code> environment variable. The output FlowFile will looke like this if we run