[jira] [Commented] (NIFI-3867) Add Expression Language support to HiveConnectionPool

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user mattyb149 opened a pull request:

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

    NIFI-3867: Add Expression Language support to HiveConnectionPool properties

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


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

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

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

    https://github.com/apache/nifi/pull/1783.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 #1783
    
----
commit 3ada739dc69aa60d344f8ba90066a019da25685c
Author: Matt Burgess <ma...@apache.org>
Date:   2017-05-11T16:56:06Z

    NIFI-3867: Add Expression Language support to HiveConnectionPool properties

----


> Add Expression Language support to HiveConnectionPool
> -----------------------------------------------------
>
>                 Key: NIFI-3867
>                 URL: https://issues.apache.org/jira/browse/NIFI-3867
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>
> The HiveConnectionPool controller service does not accept Expression Language for fields such as the JDBC URL, Resource locations, etc.  With the advent of the Variable Registry, improving these fields to accept and evaluate NiFi Expression Language (not against a flow file, but against the environment to include a variable registry) would be helpful for the development lifecycle (dev to test to production, e.g.).
> This is an extension of NIFI-2407. NIFI-2923 will handle the Kerberos properties (as they are shared amongst many processors)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)