[
https://issues.apache.org/jira/browse/NIFI-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979208#comment-14979208
]
Bryan Bende commented on NIFI-1079:
-----------------------------------
This is cool... would it provide any benefit to have another property like
"JSON Destination" which would have choices of "flowfile-attribute" or
"flowfile-content"? and then if content is selected it would overwrite the
FlowFile content instead of adding an attribute.
An example that comes to mind is making a JSON document to index in Solr, so a
flow like AttributesToJSON -> ReplaceText -> PutSolrContentStream, and then we
could eliminate the ReplaceText.
> Support AttributesToJSON processor
> ----------------------------------
>
> Key: NIFI-1079
> URL: https://issues.apache.org/jira/browse/NIFI-1079
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Randy Gelhausen
> Labels: beginner
>
> Add a standard processor for creating a new attribute on a Flowfile which is
> the JSON representation of all (default) or a user-defined list of attributes.
> Flowfile:
> foo: bar
> content: sometext
> AttributesToJSON output:
> foo: bar
> content: sometext
> JSON: {foo: 'bar', content: 'sometext'}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
