[
https://issues.apache.org/jira/browse/NIFI-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054419#comment-18054419
]
Daniel Stieglitz commented on NIFI-15501:
-----------------------------------------
[~_mark_] Have you tried configuring the ModifyCompression processor with the
Input Compression Strategy set with value "use mime.type attribute"? Per the
[NIFI
docs|https://nifi.apache.org/components/org.apache.nifi.processors.compress.ModifyCompression/]
it seems that is the feature you are looking for.
> ModifyCompression should route incoming uncompressed FlowFile appropriately
> when Input Compression Strategy is 'use mime type attribute'
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-15501
> URL: https://issues.apache.org/jira/browse/NIFI-15501
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 2.6.0
> Environment: Windows Server 2022
> Reporter: Mark Ward
> Priority: Minor
>
> ModifyCompression replaces the deprecated (as of 2,6.0) CompressContent.
> CompressContent had a useful feature, the documentation explains:
> {quote}A common idiom is to precede CompressContent with IdentifyMimeType and
> configure Mode='decompress' AND Compression Format='use mime.type attribute'.
> When used in this manner, the MIME type is automatically detected and the
> data is decompressed, if necessary. If decompression is unnecessary, the data
> is passed through to the 'success' relationship.
> {quote}
> In contrast, ModifyCompression does not behave this way, instead routing
> FlowFiles to the failure relationship (note this does not raise an
> error/bulletin).
> Can the ModifyCompression be modified to optionally include similar
> behaviour. Perhaps routing files to a separate queue if user transparency is
> is of high importance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
