Apache nifi Kylo模板失败

我已经创建了具有3个处理器的Nifi工作流。附件是详细信息。 问题是，当我在Nifi中运行工作流时，它运行正常，但当我在Kylo中导入相同的模板并通过提要运行时，它给出了错误。Kylo模板似乎有问题。你能帮我一下吗。在Nifi日志中，我也看不到任何错误

谢谢

基洛工作失败

Nifi工作流

Kylo模板-1

---

Kylo通过查看连接名称来确定流文件是否失败。由于您使用相同的连接进行失败和成功，因此Kylo无法确定这是失败还是成功

有几种方法可以改变这种情况：

为故障添加PutFile或LogAttribute处理器，并删除现有的故障连接。如果出现故障，这将停止流文件的进程

自动终止故障连接并删除现有的故障连接。这将阻止流文件进行，但Kylo将显示所有内容为成功，因为没有失败的连接

将您的连接重命名为“成功”。这将允许流文件继续，Kylo将显示所有成功的内容

---

Kylo通过查看连接名称来确定流文件是否失败。由于您使用相同的连接进行失败和成功，因此Kylo无法确定这是失败还是成功

有几种方法可以改变这种情况：

为故障添加PutFile或LogAttribute处理器，并删除现有的故障连接。如果出现故障，这将停止流文件的进程

自动终止故障连接并删除现有的故障连接。这将阻止流文件进行，但Kylo将显示所有内容为成功，因为没有失败的连接

将您的连接重命名为“成功”。这将允许流文件继续，Kylo将显示所有成功的内容

---

日志中的时间戳与Kylo UI中的故障时间不对应。你能看看你能不能匹配这两个吗？在Nifi日志中肯定有一些东西，而且这种问题最好在Kylo Google Group上提出，因为它不是严格意义上的编程类型的问题。你可以在google groups上找到Kylo社区，也可以在google groups上看到以下对话：日志中的时间戳与Kylo UI中的故障时间不对应。你能看看你能不能匹配这两个吗？在Nifi日志中肯定有一些东西，而且这种问题最好在Kylo Google Group上提出，因为它不是严格意义上的编程类型的问题。你可以在这里找到谷歌群组上的Kylo社区，也可以看到以下关于谷歌群组的对话：

    Nifi log:

    2017-08-30 10:11:49,764 INFO [pool-8-thread-1] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@65b65bdb checkpointed with 1 Records and 0 Swap Files in 34 milliseconds (Stop-the-world time = 16 milliseconds, Clear Edit Logs time = 15 millis), max Transaction ID 37082
    2017-08-30 10:11:49,764 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 1 records in 34 milliseconds
    2017-08-30 10:13:47,109 INFO [Write-Ahead Local State Provider Maintenance] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@2efe3a02 checkpointed with 2326 Records and 0 Swap Files in 18 milliseconds (Stop-the-world time = 1 milliseconds, Clear Edit Logs time = 1 millis), max Transaction ID 6977
    2017-08-30 10:13:49,764 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile Repository
    2017-08-30 10:13:49,799 INFO [pool-8-thread-1] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@65b65bdb checkpointed with 1 Records and 0 Swap Files in 34 milliseconds (Stop-the-world time = 16 milliseconds, Clear Edit Logs time = 15 millis), max Transaction ID 37082
    2017-08-30 10:13:49,799 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 1 records in 34 milliseconds
    2017-08-30 10:14:05,620 INFO [StandardProcessScheduler Thread-3] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ExecuteSQL[id=ef6f1e38-682f-4300-d33f-ceb1839cdf61] to run with 1 threads
    2017-08-30 10:14:06,147 INFO [Flow Service Tasks Thread-2] o.a.nifi.controller.StandardFlowService Saved flow controller org.apache.nifi.controller.FlowController@2678d4a7 // Another save pending = false
    2017-08-30 10:14:08,057 INFO [FeedStatisticsManager-SendStats-2] c.t.n.p.j.ProvenanceEventActiveMqWriter SENDING Batch Events to JMS ProvenanceEventRecordDTOHolder{events=3} 
    2017-08-30 10:14:14,951 INFO [Provenance Maintenance Thread-1] o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers for events starting with ID 46037
    2017-08-30 10:14:14,965 INFO [Provenance Repository Rollover Thread-2] o.a.n.p.PersistentProvenanceRepository Successfully merged 16 journal files (4 records) into single Provenance Log File /opt/data/provenance_repository/46033.prov in 18 milliseconds
    2017-08-30 10:14:14,965 INFO [Provenance Repository Rollover Thread-2] o.a.n.p.PersistentProvenanceRepository Successfully Rolled over Provenance Event file containing 3 records
    2017-08-30 10:14:38,057 INFO [FeedStatisticsManager-SendStats-0] c.t.n.p.j.ProvenanceEventActiveMqWriter SENDING Batch Events to JMS ProvenanceEventRecordDTOHolder{events=3} 
    2017-08-30 10:14:44,959 INFO [Provenance Maintenance Thread-3] o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers for events starting with ID 46041
    2017-08-30 10:14:44,999 INFO [Provenance Repository Rollover Thread-1] o.a.n.p.PersistentProvenanceRepository Successfully merged 16 journal files (4 records) into single Provenance Log File /opt/data/provenance_repository/46037.prov in 39 milliseconds
    2017-08-30 10:14:44,999 INFO [Provenance Repository Rollover Thread-1] o.a.n.p.PersistentProvenanceRepository Successfully Rolled over Provenance Event file containing 3 records