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

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

GitHub user MikeThomsen opened a pull request:

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

    NIFI-5287 Made LookupRecord able to take in flowfile attributes and c…

    …ombine them with lookup keys.
    
    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/MikeThomsen/nifi NIFI-5287

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

    https://github.com/apache/nifi/pull/2777.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 #2777
    
----
commit d841faeb4311266fe0fde28c9c6053388082024e
Author: Mike Thomsen <mikerthomsen@...>
Date:   2018-06-09T17:43:24Z

    NIFI-5287 Made LookupRecord able to take in flowfile attributes and combine 
them with lookup keys.

----


> LookupRecord should supply flowfile attributes to the lookup service
> --------------------------------------------------------------------
>
>                 Key: NIFI-5287
>                 URL: https://issues.apache.org/jira/browse/NIFI-5287
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>
> LookupRecord should supply the flowfile attributes to the lookup service. It 
> should be done as follows:
>  # Provide a regular expression to choose which attributes are used.
>  # The chosen attributes should be foundation of the coordinates map used for 
> the lookup.
>  # If a configured key collides with a flowfile attribute, it should override 
> the flowfile attribute in the coordinate map.



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

Reply via email to