Lazy Sources

Open comnik opened this issue 6 years ago • 1 comments

We should split up RegisterSource in the same vein as RegisterQuery + Interest. This would allow us store source configurations and either synthesize them in combination with a query or into an attribute.

The former would allow us to create purely streaming queries with no historical state.

Apr 09 '19 17:04 comnik

A 80/20 solution here would be to add the ability to limit the number of times an attribute might be used (e.g. once), after which the trace will be dropped from the server state. This would keep all previously created dataflows running but would prevent the accumulation of new batches.

Aug 15 '19 16:08 comnik