[
https://issues.apache.org/jira/browse/NIFI-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470068#comment-15470068
]
Raymond commented on NIFI-2579:
-------------------------------
I agree that first putting the content into an attribute is not logical. I also
have an use case where one needs to dump content or use the content in a script
or sql than one would like to do something like the following expression:
${fileContent}
or if the content isn't a string
${fileContent:toString()}
> Support accessing FlowFile content directly via expression language
> -------------------------------------------------------------------
>
> Key: NIFI-2579
> URL: https://issues.apache.org/jira/browse/NIFI-2579
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Randy Gelhausen
>
> If you want to use a FlowFile's content in routing logic, or in metadata for
> external APIs, you must use an ExtractText processor to pull the content into
> an attribute. This is confusing and seems extraneous- the natural inclination
> is to dive into expression language seeking the "content" property which
> doesn't exist today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
