You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Simon Elliston Ball (JIRA)" <ji...@apache.org> on 2016/08/15 12:27:20 UTC

[jira] [Commented] (NIFI-2465) InferAvroSchema not evaluating EL against incoming FlowFile

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

Simon Elliston Ball commented on NIFI-2465:
-------------------------------------------

This should also consider the changes in https://issues.apache.org/jira/browse/NIFI-2369 which allow delimiters to be specified in EL. These two processors (ConvertCSVToAvro and InferAvroSchema) seem very likely to be used together. I'm happy to take this on btw. 

> InferAvroSchema not evaluating EL against incoming FlowFile
> -----------------------------------------------------------
>
>                 Key: NIFI-2465
>                 URL: https://issues.apache.org/jira/browse/NIFI-2465
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.5.0, 0.5.1, 0.7.0, 0.6.1
>            Reporter: Bryan Bende
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> Many of the properties in InferAvroSchema support expression language, but don't evaluate it against an incoming flow file. 
> Some examples:
> {code}
> context.getProperty(RECORD_NAME).evaluateAttributeExpressions().getValue()
> context.getProperty(HEADER_LINE_SKIP_COUNT).evaluateAttributeExpressions().asInteger()
> context.getProperty(ESCAPE_STRING).evaluateAttributeExpressions().getValue()     
> context.getProperty(QUOTE_STRING).evaluateAttributeExpressions().getValue()
> {code}
> These should all use the incoming flow file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)