[
https://issues.apache.org/jira/browse/NIFI-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076739#comment-15076739
]
Joseph Witt commented on NIFI-1335:
-----------------------------------
I'd recommend we just use mime.type for now to be consistent with the rest and
we spin off a ticket for the 1.0.0 version to change mime.type to media.type.
> Make UnpackContent recognize tar mime type from DetectMimeType
> --------------------------------------------------------------
>
> Key: NIFI-1335
> URL: https://issues.apache.org/jira/browse/NIFI-1335
> Project: Apache NiFi
> Issue Type: Task
> 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)
