[
https://issues.apache.org/jira/browse/NIFI-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344603#comment-15344603
]
ASF GitHub Bot commented on NIFI-615:
-------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall @markap14 here is my two cents in reading this exchange. Joe's
points are really good about what a user expects and would like to see. Mark's
points are true but from a purely how it is implemented now perspective.
Basically what we should, imho, being saying is that 'Joe your idea is right
but as of now we cannot afford to do that well'. For now, it should cause a
bulletin to happen which does give the user a sense of what is happening
generally (and recently).
And we should make a JIRA to figure out how to best achieve what joe
describes. We absolutely want a dataflow manager to be able to see what went
wrong. Perhaps we say something as simple as 'we don't index route events' and
thus provenance will be ok. Or maybe we do more. Whatever it is we can do
more and it should work as joeP had hoped.
> 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
> Fix For: 1.0.0, 0.7.0
>
>
> 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)
