为什么在序列生成器或更新状态后不使用木匠 [英] Why joiner is not used after Sequence generator or Update statergy

查看:62
本文介绍了为什么在序列生成器或更新状态后不使用木匠的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

任何人都可以解释为什么在序列生成器或更新状态之后不使用木匠吗?

Can any one please explain Why joiner is not used after Sequence generator or Update statergy?

推荐答案

这是因为在这两次转换之前,joiner可能无法实现所获得的逻辑.

It's because joiner may render useless the logic achieved until those two transformation.

序列生成器之后的联接器-序列生成器的目的是生成新的或丢失的键值.根据联接类型,您可以删除此键值.

Joiner after sequence generator - Purpose of a sequence generator is to generate a new or missing key value. Depending on the join type, you may drop this key value.

更新策略后的联接器-更新策略的目的是确定需要如何将记录处理到数据库中-插入/更新/删除.通常,在提取所有数据并且应用了每个逻辑/转换后,才做出此决定.根据联接类型,您可能会错过对数据库的必要更改.

Joiner after update strategy - Purpose of update strategy is to determine how a record needs to be processed into the database - insert/update/delete. This decision generally gets made when all the data has been pulled in and every logic/transformation has been applied. Depending on the join type you might miss essential changes to your database.

这篇关于为什么在序列生成器或更新状态后不使用木匠的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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