kazoo client should be implicitly created and connected for cluster if not provided about pykafka HOT 10 CLOSED

where do you get the zookeeper hosts?

from pykafka.

I propose:

SamsaClient(zk=None, hosts=None, connection_timeout=30)

where either zk or hosts is required. connection timeout is ignored if zk is provided.

from pykafka.

where do you get the zookeeper hosts?

good point

from pykafka.

what about the threading handler
what about the zookeeper chroot
what about ACLs
what about error handling

from pykafka.

what about the threading handler
what about the zookeeper chroot
what about ACLs
what about error handling

How is this handled now?

from pykafka.

One initializes the kazoo client with applicable settings an passes it in to Samsa

Plaese forgive typos -- sent via phone

On Sep 27, 2012, at 17:53, Jeff Pollard [email protected] wrote:

what about the threading handler
what about the zookeeper chroot
what about ACLs
what about error handling

How is this handled now?

—
Reply to this email directly or view it on GitHub.

from pykafka.

One initializes the kazoo client with applicable settings an passes it in to Samsa

Right, so the issue is: if Samsa makes a Kazoo client for you, how do you specify all the requirements (ACL, threading handler, etc)?

from pykafka.

Correct

Plaese forgive typos -- sent via phone

On Sep 27, 2012, at 17:58, Jeff Pollard [email protected] wrote:

One initializes the kazoo client with applicable settings an passes it in to Samsa

Right, so the issue is: if Samsa makes a Kazoo client for you, how do you specify all the requirements (ACL, threading handler, etc)?

—
Reply to this email directly or view it on GitHub.

from pykafka.

So in talking with @tkaemming more, I learned that at the time the dependency was declared, kazoo==0.5 was actually the only working version of Kazoo that works with this code. That changes what I thought the rationale was for the version peg to 0.5, so I'm actually -1 on this change.

I still think dependency injection of the Kazoo requirement is the right story all the time. Moving forward, we should make our Kazoo requirement in Samsa be as open as is possible to support and also guarantee Samsa works - which is something we're all in agreement on I think.

from pykafka.

+1 to what Jeff said

Plaese forgive typos -- sent via phone

On Sep 27, 2012, at 18:17, Jeff Pollard [email protected] wrote:

So in talking with @tkaemming more, I learned that at the time the dependency was declared, kazoo==0.5 was actually the only working version of Kazoo that works with this code. That changes what I thought the rationale was for the version peg to 0.5, so I'm actually -1 on this change.

I still think dependency injection of the Kazoo requirement is the right story all the time. Moving forward, we should make our Kazoo requirement in Samsa be as open as is possible to support and also guarantee Samsa works - which is something we're all in agreement on I think.

—
Reply to this email directly or view it on GitHub.

from pykafka.