You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Ricky Saltzer (JIRA)" <ji...@apache.org> on 2015/12/28 23:06:49 UTC

[jira] [Updated] (NIFI-1335) Unpack Expects Invalid tar Mime Type

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

Ricky Saltzer updated NIFI-1335:
--------------------------------
    Fix Version/s: 0.5.0

> Unpack Expects Invalid tar Mime Type
> ------------------------------------
>
>                 Key: NIFI-1335
>                 URL: https://issues.apache.org/jira/browse/NIFI-1335
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Ricky Saltzer
>            Assignee: Ricky Saltzer
>            Priority: Minor
>             Fix For: 0.5.0
>
>
> While creating a pipeline using a {{DetectMimeType}} and {{UnpackContent}} processor, I noticed that the {{UnpackContent}} expects {{application/tar}} inside of the {{mime.attribute}} for tar archives, which is not correct. The Apache Tika project actually produces (1) {{application/x-tar}}.
> (1): https://tika.apache.org/1.11/api/org/apache/tika/server/writer/TarWriter.html
> This fix should be fairly simple. I propose we modify the {{UnpackContent}} processor to accept both {{application/tar}} and {{application/x-tar}} to ensure backwards compatibility with previous workflows. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)