Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detecting zero tuples flowing through a stream for the purpose of tagging #100

Open
home4slc opened this issue Mar 5, 2016 · 2 comments
Labels

Comments

@home4slc
Copy link
Contributor

home4slc commented Mar 5, 2016

I'm writing a sample where I know a stream (Stream) has no tuples, however, it's a rigged example, and I'm trying to demonstrate that there is a way to test for no tuples flowing.

If no tuples are flowing, then I want to tag it in a different way then if tuples are flowing.

I talked with @vdogaru and we got it to the point where if I put a counter on the stream that I suspect has no tuples and then after submitting the topology go through all the counters and look at their values I can see which oplets (counters) have no tuples.

But I can't figure out a way programmatically to test if a stream has no tuples, and if that is the case tag it. Anyone have any thoughts on this?

If not, I will log it as an enhancement. Thanks.

@ddebrunner
Copy link
Contributor

Currently tags are not a runtime concept, but are set at topology declaration time. So I'm not sure if it would be possible to detect no tuples flowing and then dynamically tag it.

@ddebrunner
Copy link
Contributor

Seems like a peek operator with a timed window should be able to detect if no tuples are flowing. It could then set a metric indicating if tuples are flowing or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants