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

finagle-memcached: KetamaClientBuilder - expose the client type #280

Closed
wants to merge 1 commit into from
Closed

finagle-memcached: KetamaClientBuilder - expose the client type #280

wants to merge 1 commit into from

Conversation

fwbrasil
Copy link
Contributor

In order to access the client nodes for operations like individual node stats.

@xinxiang-twitter
Copy link
Contributor

lgtm

@stevegury
Copy link
Contributor

LGTM
I'm pulling this internally, it will show up here soon.

Thanks for the contribution.

stevegury added a commit that referenced this pull request Jun 25, 2014
…he build() API

Problem

KetamaClientBuilder.build() doesn't expose the exact client type.

Solution

Expose the client type `KetamaClient` in the build() API.

from github: #280
Signed-off-by: Steve Gury <stevegury@twitter.com>- Problem

RB_ID=384391
@mosesn
Copy link
Contributor

mosesn commented Jul 2, 2014

@fwbrasil it turns out that this is a binary incompatible change, and we won't be able to do it until we do a major version bump. Although we had merged it in, we had to revert it.

suncelesta pushed a commit to suncelesta/finagle that referenced this pull request Feb 19, 2015
…he build() API

Problem

KetamaClientBuilder.build() doesn't expose the exact client type.

Solution

Expose the client type `KetamaClient` in the build() API.

from github: twitter#280
Signed-off-by: Steve Gury <stevegury@twitter.com>- Problem

RB_ID=384391
@mosesn
Copy link
Contributor

mosesn commented May 28, 2016

@fwbrasil we've stopped following semver so religiously, so I think we'd be happy to merge this in. you think it's still worth doing?

@fwbrasil
Copy link
Contributor Author

@mosesn I'd prefer to close it, I'm not sure if it'd be useful anymore.

@mosesn
Copy link
Contributor

mosesn commented May 28, 2016

Works for me. Thanks!

@mosesn mosesn closed this May 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants