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

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

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/1276

    NIFI-3095: Add EL support to Elasticsearch 2.x (and HTTP) processors

    For feature parity with the ES 5.0 processors, I added EL support to all 
appropriate properties. Also I moved the relationship and property descriptor 
creation to static blocks (as is the conventional wisdom). Unit tests were 
added to exercise the EL logic, and I changed some Java 7 constructs to Java 8 
constructs (lambdas, e.g.)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-3095

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1276.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1276
    
----
commit 3a849a0419671f81594f8a2c21d4b67f0ec357bf
Author: Matt Burgess <[email protected]>
Date:   2016-11-29T16:29:47Z

    NIFI-3095: Add EL support to Elasticsearch 2.x (and HTTP) processors

----


> 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