[ 
https://issues.apache.org/jira/browse/NIFI-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Stieglitz updated NIFI-15736:
------------------------------------
    Description: 
In the ModifyCompression and CompressContent processors, when using the 
mime.type attribute to determine the compression strategy, the application/x-xz 
mime.type is not supported.  However, the LZMA2 codec (a.k.a. "XZ-LZMA2" with 
the .xz file extension) is supported when not using the mime.type attribute.  
This appears to be an accidental omission.

This was reported in the following Slack 
[thread|https://apachenifi.slack.com/archives/C0L9VCD47/p1773838063155819]

  was:In the ModifyCompression and CompressContent processors, when using the 
mime.type attribute to determine the compression strategy, the application/x-xz 
mime.type is not supported.  However, the LZMA2 codec (a.k.a. "XZ-LZMA2" with 
the .xz file extension) is supported when not using the mime.type attribute.  
This appears to be an accidental omission.


> Mime type application/x-xz should be supported in ModifyCompression
> -------------------------------------------------------------------
>
>                 Key: NIFI-15736
>                 URL: https://issues.apache.org/jira/browse/NIFI-15736
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Michael W Moser
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>
> In the ModifyCompression and CompressContent processors, when using the 
> mime.type attribute to determine the compression strategy, the 
> application/x-xz mime.type is not supported.  However, the LZMA2 codec 
> (a.k.a. "XZ-LZMA2" with the .xz file extension) is supported when not using 
> the mime.type attribute.  This appears to be an accidental omission.
> This was reported in the following Slack 
> [thread|https://apachenifi.slack.com/archives/C0L9VCD47/p1773838063155819]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to