[
https://issues.apache.org/jira/browse/NIFI-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200741#comment-15200741
]
ASF GitHub Bot commented on NIFI-615:
-------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/252#issuecomment-198149231
@jskora do the attribute names that come from the media bundles have
anything special to them in terms of how tika handles them or are they purely
as found in the metadata of the raw entities? Just want to make sure there
isn't some special mapping/normalization to worry about as versions of tika
evolves.
Also, i've not built this yet but do you know how large those parsers end
up being when pulled in for the nar? I recall for some reason they can be
quite huge which is why we have avoided them so far. Thinking being the are
perfectly fine once we have the registry. Might be fine now too but curious.
> Create a processor to extract WAV file characteristics
> ------------------------------------------------------
>
> Key: NIFI-615
> URL: https://issues.apache.org/jira/browse/NIFI-615
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Brandon DeVries
> Assignee: Joe Skora
> Priority: Minor
>
> Create a processor to extract information from a WAV file, including
> encoding, bit rate, metadata, etc...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
