LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only

  • 1.  Meta Check node is causing all nodes past it to clear whenever a node is run

    Employee
    Posted 06-07-2016 23:02

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: dglavastorm

    Hi - I have a very strange behaviour occurring on one of my Meta Check nodes. The node is set to ClockWithPropagate.

    Any time any node after this one is run or rerun, even miles and many nodes down the graph track, the Meta Check node clears and re-runs which of course clears every node clocked or joined after it.

    This means that I to continuing building the graph I've had to create a static output after the Meta Join nodes, then bring this back in with no clock or join to the output. Any connection, clock or join, causes the same issue.

    What's even stranger is I have the exact same node earlier in the graph, but this only occurs back to the second one.

    Is this a glitch or something I'm missing ?

    Thanks,
    Dave


  • 2.  RE: Meta Check node is causing all nodes past it to clear whenever a node is run

    Employee
    Posted 06-08-2016 06:49

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: gmullin

    Are you able to post a small example of this, no need for your entire graph? Just a couple of nodes before the meta check and after it (that will run start to finish).


  • 3.  RE: Meta Check node is causing all nodes past it to clear whenever a node is run

    Employee
    Posted 06-08-2016 16:42

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: dglavastorm

    Hi Gmullin - Overnight I've found the cause - it's not related to the Metadata node, it's a custom Teradata Fastload python node that for some reason always clears the nodes after it even though the node itself doesn't run.

    I'll have to go back to the authors - is there any way to delete this thread as it's not a LS problem ?