闭环在 Talend 作业中不起作用 [英] Closed loop does not work in a Talend Job

查看:36
本文介绍了闭环在 Talend 作业中不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个 Talend 作业,其中组件以某种方式形成了一个闭环.图片如下:

I have a Talend Job, where somehow a closed loop is formed by the components. Image is as follows:

两个 tMap 输出的模式是相同的.现在将任何 tMap 连接到 tUnite 后,当我尝试连接第二个 tMap 时,它没有连接到它.我听说 Talend 不允许,一个 Job 中的一个闭环.真的吗?如果是,为什么?有人在此处提出了类似的问题,但没有找到答案.>

The schemas of both the tMap outputs is same. Now after connecting any tMap to tUnite, when I try to connect the second tMap, it does not connect to it. I heard that Talend does not allow, a closed loop in a Job. Is that true? If yes, the Why? Someone had a similar question here, but found no answers.

推荐答案

Talend 实际上创建了一个 Java 程序;基本上这就是您遇到的限制的原因.

Talend actually creates a Java program; essentially that is the reason for the limitation you've encountered.

tUnite 依次获取每个输入提供的所有数据,即所有 A 然后所有 B 然后所有 C.

tUnite take all the data provided by each of the inputs in turn i.e. all of A then all of B then all of C.

由于用于每个流程的编程循环的性质,它不能从 A 取第 1 行,然后从 B 取第 1 行,然后从 C 取第 1 行,然后从 A 取第 2 行,然后从 B 取第 2 行,等等.但是,tMap 多个输出或 tReplicate 确实创建了第 1 行到 A,然后是第 1 行到 B,然后是第 1 行到 C,然后是第 2 行到 A,然后是第 2 行到 B 等等.

It cannot take row 1 from A then row 1 from B then row 1 from C then row 2 from A then row 2 from B etc. because of the nature of programming loops used for each flow. However, tMap multiple outputs or tReplicate do create row 1 to A then row 1 to B then row 1 to C then row 2 to A then row 2 to B etc..

这就是您不能拆分然后重新加入流的原因.

This is why you cannot split and then rejoin flows.

这篇关于闭环在 Talend 作业中不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆