| Author |
Message
|
| ghoshly |
 Posted: Tue Aug 03, 2010 12:31 am Post subject: PROPAGATE in Filter node |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I have used a propagate statement in a filter node..
| Code: |
| PROPAGATE To Terminal 'True' ; |
This does not gives any syntax error as there is no problem in the PROPAGATE statement. Nothing in deployment time also, so as in run time.
I believe it just runs into a infinite loop causing problematic to stop the flow or even undeploy the same.
From documentation I came to know that I should not use PROPAGATE statement inside Filter node and I did accordingly.
| Quote: |
| You can use the PROPAGATE statement in Compute and Database nodes, but not in Filter nodes |
My question is why that one is not supported in Filter node, If not supported why it is not throwing an exception as well on the statement.[/quote] |
|
| Back to top |
|
 |
| Mandeep |
| Posted: Tue Aug 03, 2010 2:19 am Post subject: |
|
|
Apprentice
Joined: 03 May 2004
Posts: 33
|
With Filter node you cannot change the contents of the message, so the incoming message will come out as it is from the Filter node.
PROPAGATE is used when you have to send multiple messages out with different content possibly. |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Aug 03, 2010 2:52 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
As per my knowledge its not PROPAGATE's business about the content of the tree its sending to the next connected terminal, just sends the current one.
Expecting the reason of the problem. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 03, 2010 3:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| ghoshly wrote: |
| Expecting the reason of the problem. |
You can expect all you want.
Reread what the job of the filter node is, and what it is designed to be used for. It doesn't make sense to use PROPAGATE inside a Filter node. It really doesn't. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 03, 2010 4:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ghoshly wrote: |
| Expecting the reason of the problem. |
The problem is the documentation correctly states you can't use that statement in a Filter node (and as my most worthy associate points out it doesn't make sense to) but neither the toolkit nor the runtime is blocking it.
You should raise a PMR against one or the other (or both). My preference would be the Toolikit but that's just a personal thing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Aug 03, 2010 7:03 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I am sorry if I made someone angry with my question, but my intension was to know and understand the implementation (like mapping node which inturn generates esql) so that why it is not throwing any error / exception.
Documentation is clearly written that we can't use that statement in Filter node, no problem with that. Just wanted to have the reason behind that because for some cases when we want some loops / repetition (series of node / subflow) we could have used that statement with the filter node before hand( I believe filter is lighter than compute, pls correct me if I am wrong)
Thanks for your help / guidance / suggestion.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 03, 2010 7:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ghoshly wrote: |
| Just wanted to have the reason behind that because for some cases when we want some loops / repetition (series of node / subflow) we could have used that statement with the filter node before hand |
You still can. Think about it.
| ghoshly wrote: |
| I believe filter is lighter than compute, pls correct me if I am wrong) |
It's a shaved down compute node. You'd need a really accurate stopwatch to tell the difference. The biggest difference is the Filter node doesn't spend time to build an output tree but like I said, that's a minimal overhead.
I still think you'd be justified in raising a PMR against Toolkit. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
