Syndesis: Consider adding check for cycles

[Stefan365]

[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Documentation issue or request

The problem

There is no warning / restriction for user if he selects autoreference with positive feedback route.
i.e. result is added into source,
so that message volume is doubling every reading period.

Expected behavior

autoreference prohibited. Or with warning at least.

Tasks involved / Steps to Reproduce

1. create DB to DB integrations Create DB to DB(Periodic SQL invocation/Invoke SQL) integration with datamapper step.
   use: "SELECT * FROM TODO" for start action Periodic SQL invocation
   and "INSERT INTO TODO(task, completed) VALUES (:#TASK, 0)" for finish action Invoke SQL
   and invocation period 1000ms.

2. Add datamapper step, and map task to TASK.

3. publish integration
4. Look, what's going to happen.

[deeleman]

This issue just won the "Best attention-seeker title" award 😆

[KurtStam]

Step 4 should have read: "You won't believe what's going to happen"

[KurtStam]

To "save you a click": In 50 steps the number of rows in the database outweighs the earth and a black hole opens up.

[gashcrumb]

I'm trying this now just to watch my minishift instance burn.

TBH I think this is a worthwhile feature.

[gashcrumb]

See, it's a great disk performance tool:

weeeeee!

[KurtStam]

Goodbye my friend - it was nice working with you

[kahboom]

OMG this thread cracked me the hell up...

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!