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

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

GitHub user ijokarumawak opened a pull request:

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

    NIFI-3404: LookupAttribute, SimpleCsvFileLookupService, 
PropertiesFileLookupService, XMLFileLookupService

    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)?
    
    - [ ] 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?
    - [x] 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?
    - [x] 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:
    - [x] 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/ijokarumawak/nifi nifi-3404

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

    https://github.com/apache/nifi/pull/1856.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 #1856
    
----
commit 86d4198ce5537387a375e23003c8265be2c1e14d
Author: Joey Frazee <jfra...@apache.org>
Date:   2017-05-19T16:45:14Z

    NIFI-3404 Added LookupAttribute processor and lookup controller services

commit 4f81af0961c3d65c4df37b9de3934c8fed1a70ff
Author: Koji Kawamura <ijokaruma...@apache.org>
Date:   2017-05-25T04:22:54Z

    NIFI-3404: Improved UX of LookupAttributes.
    
    - Added dependency notice.
    - Added EL evaluation at SimpleKeyValueLookupService.
    - Updated documentation.
    - Updated CommonsConfigurationLookupService to throw LookupFailureException 
if it fails to get configuration so that error messages can be displayed at 
each processor bulletin.
    - Added calling getConfiguration at OnEnabled of 
CommonsConfigurationLookupService, so that the service will stay in Enabling 
state if there is any issue.

----


> Add lookup processor for enrichments/joins to reference data
> ------------------------------------------------------------
>
>                 Key: NIFI-3404
>                 URL: https://issues.apache.org/jira/browse/NIFI-3404
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joey Frazee
>            Assignee: Joey Frazee
>
> NiFi doesn't currently have an easy, concise way of doing enrichment, joining 
> against reference data sets or performing attribute lookups against external 
> data sources.
> Since enrichments and joins are basic streaming use cases, and since 
> attributes and EL are often used to parameterize processor properties, there 
> is a need for an easy way to do enrichments, joins and lookups without having 
> to write code or create a lengthy data flow.
> There's been some discussion of this on the mailing list [1] and I've started 
> work on a LookupAttribute [2] processor that delegates the work to controller 
> services.
> 1. 
> https://lists.apache.org/thread.html/74321ff0e9e0b7339e43ad53b36119315dc5094991605edfb12b34d0@%3Cdev.nifi.apache.org%3E
> 2. https://github.com/jfrazee/nifi-lookup-service



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

Reply via email to