简体繁体 English

NiFi：查看流文件

[英]NiFi: View Flow File

原文 2017-01-09 15:04:09 6 1 apache-nifi

I'm just getting started with NiFi, and it's great when things work first shot. 我刚刚开始使用NiFi，当第一次拍摄时它很棒。

When things fail, I'd like to view the flow file, or the output (stdout+stderr) from the problematic processor. 当事情失败时，我想从有问题的处理器中查看流文件或输出（stdout + stderr）。 Is there an easy way to dump out all of the flow file's properties, or to just browse a flow file? 是否有一种简单的方法来转储所有流文件的属性，或只是浏览流文件？

I feel like I've missed something incredibly obvious, but most of the tutorials just walk though examples where everything works first shot. 我觉得我错过了一些非常明显的东西，但是大多数教程只是走过一切都是第一次拍摄的例子。

1 个解决方案

Processors usually have one or more relationships for failures and it is up to the data flow designer to determine what to do with these. 处理器通常具有一个或多个故障关系，由数据流设计者决定如何处理这些故障。

Some failures are due to temporary conditions like if a destination system was down, for those they would typically be looped back to the same processor to keep retrying until the destination comes back up. 某些故障是由于临时条件造成的，例如目标系统是否已关闭，因为它们通常会循环回同一处理器以继续重试，直到目标恢复为止。

Other failures are due to issues related to the data and likely don't make sense to retry because they will continue to fail. 其他失败是由于与数据相关的问题，并且可能没有意义重试，因为它们将继续失败。 This set of failures you can route to PutFile processor to write them out to directory somewhere, or a PutEmail processor to notify you. 这组故障可以路由到PutFile处理器将它们写到某个目录，或者PutEmail处理器通知你。 Either of those would give you access to the raw data. 这些中的任何一个都可以让您访问原始数据。 If you want to see the flow file attributes you could use data provenance to look at all the flow files that passed through the PutFile/PutEmail processor. 如果要查看流文件属性，可以使用数据来源查看通过PutFile / PutEmail处理器传递的所有流文件。