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

Send data with api.sendToStreamId() #66

Open
pwatchara opened this issue Feb 23, 2016 · 3 comments
Open

Send data with api.sendToStreamId() #66

pwatchara opened this issue Feb 23, 2016 · 3 comments

Comments

@pwatchara
Copy link

There seem to be some difficulty when an operator who has more than one downstream operator tries to call api.sendToStreamId() to selectively send data to a particular streamId.
In addition, WorkerShutdownHookWorker is later triggered when calling the method.

(When the operator has only one downstream operator, api.send() works fine.)

@pwatchara
Copy link
Author

More comments:

I noticed that, in Collector class, buffers is currently used for api.sendToStreamId() but I believe it should be streamId_To_OBuffer instead. At the same time, I am not sure if Router is needed here as there is nothing related to the concept of key.

However, when I use streamId_To_OBuffer, ((EventBasedOBuffer)ob).getEventAPI() returns null but I don't fully understand the importance of EventAPI.

@raulcf
Copy link
Owner

raulcf commented Mar 10, 2016

What is the status of this issue?

@pwatchara
Copy link
Author

So far I noticed that the process of initialising Map buffers (in Collector class) involves using the same keys (Integer) for different entries (Therefore overwriting the previous entry).
According to CoreOutputFactory.buildCoreOutputFor(), this (Integer) key seems to be based on DataReference.getId() but the id the method returns is essentially the operatorId itself (i.e. it is the same for any downstreams.) I do not fully understand why DataReference dr is initialised so. Still work in progress.

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

No branches or pull requests

2 participants