[
https://issues.apache.org/jira/browse/NIFI-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330575#comment-15330575
]
Christopher McDermott commented on NIFI-2023:
---------------------------------------------
Ahh. That's brilliant, Joe. I didn't even know about IdentifyMimeType.
Thanks. I will withdraw this JIRA.
> CompressContent Processor should not always log decompression failures as an
> ERROR
> ----------------------------------------------------------------------------------
>
> Key: NIFI-2023
> URL: https://issues.apache.org/jira/browse/NIFI-2023
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Core UI
> Affects Versions: 0.6.1
> Reporter: Christopher McDermott
> Priority: Minor
>
> Sometimes you don't you don't know if file compression is used or what kind
> of compression is used. In these cases it is normal I think to chain
> together a bunch CompressContent processors via the the failed output to
> attempt decompression. If a stage fails in the chain it is not desirable to
> emit and ERROR bulletin.
> Perhaps a configuration parameter could be added to control the level at
> which the failure is logged. See NIFI-1724 for a similar enhancement request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
