[
https://issues.apache.org/jira/browse/NIFI-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054597#comment-18054597
]
Mark Ward commented on NIFI-15501:
----------------------------------
[~exceptionfactory] correct, that was the conclusion I came to also. However
CompressContent in decompress mode works differently. Instead it routes the
FlowFile to success with a non-compressed mime type.
Such a solution would work fine for me. - my flow does occasionally received
files that are gzip compressed due to their size, while typically they're CSV.
Being able to allow a single processor conditionally decompress the files based
on the preceding IdentifyMimeType processor is convenient.
> 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
> Attachments: image-2026-01-26-20-40-08-255.png,
> image-2026-01-26-20-40-44-013.png, image-2026-01-26-20-41-07-076.png
>
>
> 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)
