MikeThomsen commented on code in PR #6903:
URL: https://github.com/apache/nifi/pull/6903#discussion_r1175887211


##########
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-restapi-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractPutElasticsearch.java:
##########
@@ -67,13 +71,29 @@ public abstract class AbstractPutElasticsearch extends 
AbstractProcessor impleme
         .required(true)
         .build();
 
+    static final PropertyDescriptor OUTPUT_ERROR_RESPONSES = new 
PropertyDescriptor.Builder()
+            .name("put-es-output-error-responses")
+            .displayName("Output Error Responses")
+            .description("If this is enabled, response messages from 
Elasticsearch marked as \"error\" will be output to the \"error_responses\" 
relationship." +
+                    "This does not impact the output of flowfiles to the 
\"success\" or \"errors\" relationships")
+            .allowableValues("true", "false")
+            .defaultValue("false")
+            .addValidator(StandardValidators.BOOLEAN_VALIDATOR)
+            .build();
+
     static final Relationship REL_SUCCESS = new Relationship.Builder()
             .name("success")
             .description("All flowfiles that succeed in being transferred into 
Elasticsearch go here. " +
                     "Documents received by the Elasticsearch _bulk API may 
still result in errors on the Elasticsearch side. " +
                     "The Elasticsearch response will need to be examined to 
determine whether any Document(s)/Record(s) resulted in errors.")
             .build();
 
+    static final Relationship REL_ERROR_RESPONSES = new Relationship.Builder()
+            .name("error_responses")

Review Comment:
   This should be autoterminated because it changes the behavior.



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to