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

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

Github user ijokarumawak commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1830#discussion_r117677184
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/main/java/org/apache/nifi/lookup/SimpleKeyValueLookupService.java
 ---
    @@ -41,7 +48,9 @@ protected PropertyDescriptor 
getSupportedDynamicPropertyDescriptor(final String
                 .name(propertyDescriptorName)
                 .required(false)
                 .dynamic(true)
    -            .addValidator(Validator.VALID)
    +            
.addValidator(StandardValidators.createAttributeExpressionLanguageValidator(AttributeExpression.ResultType.STRING,
 true))
    +            
.addValidator(StandardValidators.ATTRIBUTE_KEY_PROPERTY_NAME_VALIDATOR)
    --- End diff --
    
    I think we can remove ATTRIBUTE_KEY_PROPERTY_NAME_VALIDATOR. The dynamic 
properties of this processor are not representing FlowFile attribute names. It 
is a little bit misleading.


> 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