[
https://issues.apache.org/jira/browse/NIFI-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980851#comment-14980851
]
Charlie Frasure commented on NIFI-1077:
---------------------------------------
Is this functionality something that could be expanded to the other processors,
or would that be another issue? ConvertCSVToAvro, ExtractText, ReplaceText
expression text are all false, while ExtractHL7Attributes is true.
It would also be nice to have an option for "Auto" that took a best guess at
character encoding, but that is certainly a larger undertaking, and probably
violates best practice.
> Allow ConvertCharacterSet to accept expression language
> -------------------------------------------------------
>
> Key: NIFI-1077
> URL: https://issues.apache.org/jira/browse/NIFI-1077
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Priority: Minor
> Attachments: NIFI-1077.patch
>
>
> This issue arose from a user on the mailing list. It demonstrates the need to
> be able to use expression language to set the incoming (and potentially
> outgoing) character sets:
> I'm looking to process many files into common formats. The source files are
> coming in various character sets, mime types, and new line terminators.
> My thinking for a data flow was along these lines:
> GetFile (from many sub directories) ->
> ExecuteStreamCommand (file -i) ->
> ConvertCharacterSet (from previous command to utf8) ->
> ReplaceText (to change any \r\n into \n) ->
> PutFile (into a directory structure based on values found in the original
> file path and filename)
> Additional steps would be added for archiving a copy of the original,
> converting xml files, etc.
> Attempting to process these with Nifi leaves me confused as to how to process
> within the tool. If I want to ConvertCharacterSet, I have to know the input
> type. I setup a ExecuteStreamCommand to file -i
> ${absolute.path:append(${filename})} which returned the expected values. I
> don't see a way to turn these results into input for the processor, which
> doesn't accept expression language for that field.
> I also considered ConvertCSVToAvro as an interim step but notice the same
> issue. Any suggestions what this dataflow should look like?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
