预期？主机管道以不同方式处理活动失败和管道故障 [英] Expected? Activity failure and pipeline failure handled differently by host pipeline

问题描述

Execute Pipeline和其他活动如何处理失败输出之间似乎存在不一致。

There appears to be an inconsistency between how Execute Pipeline and other activities handle the failure output.

Case1：如果我有一个包含Web活动之类活动的主机管道 假设活动超时或失败。 无论我是将故障输出指向另一个活动（例如"等待"）还是保持未连接，那么
主机管道返回失败，内部活动失败.....

Case1: If I have a host pipeline that contains an activity like Web activity.  Say that activity times out or fails.  Irrespective of whether I direct the failure output to another activity (say "Wait") or leave it unconnected, then the host pipeline returns failure, an inner activity failed.....

案例2：如果我通过调用Execute Pipeline替换上述Web活动并且失败，那么我将此执行管道活动的失败输出定向到另一个活动，如上面的Wait，然后主机管道不会失败。  在这种情况下，
看起来失败已被"消耗"。将故障输出连接到活动的性质。 如果我删除了与等待活动的失败连接，那么主机管道将如上所述失败。

Case2: If I replace the above Web activity with a call to Execute Pipeline and that fails, then I direct the failure output of this execute pipeline activity to another activity like Wait as above, then the host pipeline does not fail.  In this case, it appears the failure has been "consumed" by nature of connecting the failure output to an activity.  If I remove that failure connection to the wait activity, then the host pipeline fails as above.

为什么我要问？ 在某些情况下，我希望活动失败，所以我假设我使用失败连接来执行此操作。 对于管道活动，它是有效的，对于其他人则不然。 



实例 - 我调用REST api来扩展数据仓库并且无法扩展，我仍然希望运行摄取，即使DWH没有扩大规模。 我将故障输出和成功输出连接到下一个活动（或者我可以连接
teh完成连接器）。 为了解决上述问题，我必须将这个REST Web活动包装在子管道中。

Why am I asking?  In some cases, I want an activity's failure to be consumed so I assume I use the failure connection to do this.  For pipeline activity it works, for others it does not. 

Real example - I call a REST api to scale up a data warehouse and it fails to scale, I still want to run the ingestion even though the DWH did not scale up.  I connect both the failure output and the success output to the next activity (or I could connect teh completion connector).  In order to work around the above behavior, I have to wrap this REST web activity in a child pipeline.

在我看来，使用失败输出应该是一致的。 想法？

Seems to me like the use of the failure output should be consistent.  thoughts?

问候，

马克。

推荐答案

<你好，

你试过设置'waitOnCompletion'
as 是吗？此属性定义执行管道活动执行是否等待内部管道执行完成。如果将
此值设置为true，您将看到执行活动的运行状态是其内部管道，这意味着内部管道将决定执行活动运行失败或成功。

这篇关于预期？主机管道以不同方式处理活动失败和管道故障的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！