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

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

GitHub user pvillard31 opened a pull request:

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

    NIFI-5233 - Add EL support with Variable Registry scope for HBase cli…

    …ent service
    
    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:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] 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.
    
    - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [ ] 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/pvillard31/nifi NIFI-5233

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

    https://github.com/apache/nifi/pull/2738.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 #2738
    
----
commit 5d69838848be70530709aefe064b0f05cff2b6e8
Author: Pierre Villard <pierre.villard.fr@...>
Date:   2018-05-24T14:42:27Z

    NIFI-5233 - Add EL support with Variable Registry scope for HBase client 
service

----


> Enable expression language in Hadoop Configuration Files property of Hbase 
> Client Service
> -----------------------------------------------------------------------------------------
>
>                 Key: NIFI-5233
>                 URL: https://issues.apache.org/jira/browse/NIFI-5233
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.6.0
>            Reporter: Gergely Devai
>            Assignee: Pierre Villard
>            Priority: Minor
>              Labels: easyfix
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In some Hadoop related processors (e.g. GetHDFS, DeleteHDFS) the "Hadoop 
> Configuration Files" property supports expression language. This is 
> convenient, as the lengthy paths to the config files can be stored in a 
> property file loaded by Nifi at startup or in an environment variable, and 
> the name of the property/environment variable can be referenced in the 
> processors' configuration.
> The controller service HBase_1_1_2_ClientService also has the "Hadoop 
> Configuration Files" property, but it does not support expression language. 
> For the convenience reasons described above and for uniformity, it is 
> desirable to allow expression language in that property as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to