[
https://issues.apache.org/jira/browse/NIFI-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706811#comment-15706811
]
ASF GitHub Bot commented on NIFI-3095:
--------------------------------------
Github user jtstorck commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1276#discussion_r90133302
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchProcessor.java
---
@@ -28,14 +29,20 @@
import java.util.Collection;
import java.util.HashSet;
-import java.util.Map;
import java.util.Set;
/**
* A base class for all Elasticsearch processors
*/
public abstract class AbstractElasticsearchProcessor extends
AbstractProcessor {
+ protected static final Validator NON_EMPTY_EL_VALIDATOR = (subject,
value, context) -> {
--- End diff --
Assuming that this validator would provide value in other processors, it
might make sense to move this into StandardValidators?
> PutElasticSearch (2.x Bulk API) - Add expression language support to
> 'Elasticsearch Hosts' and 'Cluster Name' fields
> --------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3095
> URL: https://issues.apache.org/jira/browse/NIFI-3095
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Randy Bovay
> Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> Being able to a) Use Expression Language in the Hoss field, and ClusterName
> fields.
> This way we can provide a variable input to the service, and have it differ
> in our different data centers and environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
