[ 
https://issues.apache.org/jira/browse/NIFI-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706954#comment-15706954
 ] 

ASF GitHub Bot commented on NIFI-3095:
--------------------------------------

Github user mattyb149 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1276#discussion_r90141491
  
    --- Diff: 
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchProcessor.java
 ---
    @@ -74,8 +83,9 @@
             Set<ValidationResult> results = new HashSet<>();
     
             // Ensure that if username or password is set, then the other is 
too
    -        Map<PropertyDescriptor, String> propertyMap = 
validationContext.getProperties();
    -        if (StringUtils.isEmpty(propertyMap.get(USERNAME)) != 
StringUtils.isEmpty(propertyMap.get(PASSWORD))) {
    +        String userName = 
validationContext.getProperty(USERNAME).evaluateAttributeExpressions().getValue();
    +        String password = 
validationContext.getProperty(PASSWORD).evaluateAttributeExpressions().getValue();
    --- End diff --
    
    Oops, yes!


> 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)

Reply via email to