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

thread context at physical operator isn't deleted with the exit of the corresponding thread #97

Open
fzhedu opened this issue Nov 16, 2015 · 1 comment
Labels

Comments

@fzhedu
Copy link
Member

fzhedu commented Nov 16, 2015

because some variable need to be used in different methods, it's necessary to create context for different thread, but if the thread is callbacked and to exit the work at present, the corresponding thread context need to be deleted.
in addition, one thread may run an operator many times in different lifetime result from the corresponding thread has been callbacked in threadpoll.

@fzhedu fzhedu added the bug label Nov 16, 2015
@fzhedu
Copy link
Member Author

fzhedu commented Apr 11, 2016

after finishing next(), then there should be cleanup() to clean the corresponding context.

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

1 participant