[
https://issues.apache.org/jira/browse/NIFI-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709187#comment-15709187
]
ASF GitHub Bot commented on NIFI-3095:
--------------------------------------
Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/1276
URL Connections aren't explicitly closed in these ElasticSearch processors.
It's outside the scope of this PR, since this issue existed prior to enabling
EL on these properties. The responses from the connections pull all the bytes
at once (and are implicitly closed), so it's technically OK at this point, but
I think explicit calls to close the connections should be added for cleanliness.
> 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)
