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

In thread pools, use DirectExecutor instead of deprecated API #7636

Merged
merged 1 commit into from Sep 10, 2014

Conversation

Projects
None yet
3 participants
@s1monw
Copy link
Contributor

s1monw commented Sep 8, 2014

Guava deprecated MoreExecutors#sameThreadExecutor in favour of
a more efficient implementation. We should move over to the new impl.

@clintongormley clintongormley changed the title [ThreadPool] Use DirectExecutor instead of deprecated API Internal: In thread pools, use DirectExecutor instead of deprecated API Sep 8, 2014

@spinscale

This comment has been minimized.

Copy link
Member

spinscale commented Sep 9, 2014

LGTM

[ThreadPool] Use DirectExecutor instead of deprecated API
Guava deprecated MoreExecutors#sameThreadExecutor in favour of
a more efficient implemenation. We should move over to the new impl.

@s1monw s1monw force-pushed the s1monw:use_direct_executor branch to cb839b5 Sep 10, 2014

@s1monw s1monw merged commit cb839b5 into elastic:master Sep 10, 2014

@s1monw s1monw removed the review label Sep 10, 2014

@clintongormley clintongormley changed the title Internal: In thread pools, use DirectExecutor instead of deprecated API In thread pools, use DirectExecutor instead of deprecated API Jun 7, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.