SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL=zk1.mycompany.com:2181 confluent/schema-registry We have an environment that already uses Kafka and Zookeeper (this would be a pretty common situation I think for people in companies tied to a standard distro with ambari/other).
I am trying to encourage people to move towards confluent, starting with the schema registry - if possible as a container since most of our ancilliary apps run in containers.
This works with our current kafka version:
docker run --net="host" -eSCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL=zk1.mycompany.com:2181 confluent/schema-registry
Couple of questions:
1. Is the confluent/schema-registry image an official supported image?
- don't see tags on it for different versions, etc so it looks kind of experimental - i.e. any way to get 2.0.0 image
- another chap cgwong seems to have a more recently updated registry - seems liek a fork of your one, but not keen on using unsolicited containers.
2. Is there a kafka/zookeeper/schema-registry/rest-proxy compatibility matrix anywhere? Which version of Kafka / ZK do we need to be running to be able to run e.g. 2.0.0 schema registry (albeit the container seems to be a 1.0 ver at the moment)
- currently we run 0.8.2.2 - does this mean that I need to wait for 0.9.0 to go to 2.0 or..?
Any tips appreciated!
Cheers!
Mark.
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Tue, Feb 2, 2016 at 4:31 AM, Mark Davis <> wrote:We have an environment that already uses Kafka and Zookeeper (this would be a pretty common situation I think for people in companies tied to a standard distro with ambari/other).
I am trying to encourage people to move towards confluent, starting with the schema registry - if possible as a container since most of our ancilliary apps run in containers.
This works with our current kafka version:
docker run --net="host" -eSCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL=zk1.mycompany.com:2181 confluent/schema-registry
Couple of questions:
1. Is the confluent/schema-registry image an official supported image?
- don't see tags on it for different versions, etc so it looks kind of experimental - i.e. any way to get 2.0.0 image
- another chap cgwong seems to have a more recently updated registry - seems liek a fork of your one, but not keen on using unsolicited containers.These aren't supported at the moment, which is why we haven't published any 2.0 images. We're maintaining them on a best-effort basis right now.That said, we're keeping track of when people are using them to understand demand -- knowing you're using them is useful info!
2. Is there a kafka/zookeeper/schema-registry/rest-proxy compatibility matrix anywhere? Which version of Kafka / ZK do we need to be running to be able to run e.g. 2.0.0 schema registry (albeit the container seems to be a 1.0 ver at the moment)
- currently we run 0.8.2.2 - does this mean that I need to wait for 0.9.0 to go to 2.0 or..?These get a bit complicated because of the dependencies between them, so we provide the following docs to try to help: http://docs.confluent.io/2.0.0/upgrade.html In general, schema registry and REST proxy include *Kafka clients*, which require that the Kafka brokers be updated first. Since REST proxy depends on Schema Registry if you're using Avro messages, you'll need to upgrade Schema Registry after Kafka brokers and before REST proxy instances. I'll defer to the linked upgrade guide, but please ask if anything in the guide is unclear or incomplete and we'll try to clear it up.-Ewen
Any tips appreciated!
Cheers!
Mark.
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
Thanks Ewen, that's useful. So basically from that we can't look at 2.x until we upgrade our kafka to .9x, good to know!
Looking forward to officially supported containers at some stage!
On Friday, February 5, 2016 at 8:28:51 AM UTC, Ewen Cheslack-Postava wrote:
On Tue, Feb 2, 2016 at 4:31 AM, Mark Davis <> wrote:We have an environment that already uses Kafka and Zookeeper (this would be a pretty common situation I think for people in companies tied to a standard distro with ambari/other).
I am trying to encourage people to move towards confluent, starting with the schema registry - if possible as a container since most of our ancilliary apps run in containers.
This works with our current kafka version:
docker run --net="host" -eSCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL=zk1.mycompany.com:2181 confluent/schema-registry
Couple of questions:
1. Is the confluent/schema-registry image an official supported image?
- don't see tags on it for different versions, etc so it looks kind of experimental - i.e. any way to get 2.0.0 image
- another chap cgwong seems to have a more recently updated registry - seems liek a fork of your one, but not keen on using unsolicited containers.These aren't supported at the moment, which is why we haven't published any 2.0 images. We're maintaining them on a best-effort basis right now.That said, we're keeping track of when people are using them to understand demand -- knowing you're using them is useful info!
2. Is there a kafka/zookeeper/schema-registry/rest-proxy compatibility matrix anywhere? Which version of Kafka / ZK do we need to be running to be able to run e.g. 2.0.0 schema registry (albeit the container seems to be a 1.0 ver at the moment)
- currently we run 0.8.2.2 - does this mean that I need to wait for 0.9.0 to go to 2.0 or..?These get a bit complicated because of the dependencies between them, so we provide the following docs to try to help: http://docs.confluent.io/2.0.0/upgrade.html In general, schema registry and REST proxy include *Kafka clients*, which require that the Kafka brokers be updated first. Since REST proxy depends on Schema Registry if you're using Avro messages, you'll need to upgrade Schema Registry after Kafka brokers and before REST proxy instances. I'll defer to the linked upgrade guide, but please ask if anything in the guide is unclear or incomplete and we'll try to clear it up.-Ewen
Any tips appreciated!
Cheers!
Mark.
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--Thanks,
Ewen
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
--
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
--
--
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/4f54b99c-3af3-4889-bc2f-c73135b80356%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
--
--
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/4f54b99c-3af3-4889-bc2f-c73135b80356%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
--
--
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/4f54b99c-3af3-4889-bc2f-c73135b80356%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/0d4b6a6f-779e-41cf-bff4-d8ce45682515%40googlegroups.com.
--
--
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/4f54b99c-3af3-4889-bc2f-c73135b80356%40googlegroups.com.
This email, including attachments, is private and confidential. If you have received this email in error please notify the sender and delete it from your system. Emails are not secure and may contain viruses. No liability can be accepted for viruses that might be transferred by this email or any attachment. Any unauthorised copying of this message or unauthorised distribution and publication of the information contained herein are prohibited.
7digital Limited. Registered office: 69 Wilson Street, London EC2A 2BB.
Registered in England and Wales. Registered No. 04843573.
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/64f1c14b-675d-43fd-8e48-a59aa64e5e4c%40googlegroups.com.
On Tue, Feb 2, 2016 at 4:31 AM, Mark Davis <mark....@gmail.com> wrote:We have an environment that already uses Kafka and Zookeeper (this would be a pretty common situation I think for people in companies tied to a standard distro with ambari/other).
I am trying to encourage people to move towards confluent, starting with the schema registry - if possible as a container since most of our ancilliary apps run in containers.
This works with our current kafka version:
docker run --net="host" -eSCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL=zk1.mycompany.com:2181 confluent/schema-registry
Couple of questions:
1. Is the confluent/schema-registry image an official supported image?
- don't see tags on it for different versions, etc so it looks kind of experimental - i.e. any way to get 2.0.0 image
- another chap cgwong seems to have a more recently updated registry - seems liek a fork of your one, but not keen on using unsolicited containers.These aren't supported at the moment, which is why we haven't published any 2.0 images. We're maintaining them on a best-effort basis right now.That said, we're keeping track of when people are using them to understand demand -- knowing you're using them is useful info!
2. Is there a kafka/zookeeper/schema-registry/rest-proxy compatibility matrix anywhere? Which version of Kafka / ZK do we need to be running to be able to run e.g. 2.0.0 schema registry (albeit the container seems to be a 1.0 ver at the moment)
- currently we run 0.8.2.2 - does this mean that I need to wait for 0.9.0 to go to 2.0 or..?These get a bit complicated because of the dependencies between them, so we provide the following docs to try to help: http://docs.confluent.io/2.0.0/upgrade.html In general, schema registry and REST proxy include *Kafka clients*, which require that the Kafka brokers be updated first. Since REST proxy depends on Schema Registry if you're using Avro messages, you'll need to upgrade Schema Registry after Kafka brokers and before REST proxy instances. I'll defer to the linked upgrade guide, but please ask if anything in the guide is unclear or incomplete and we'll try to clear it up.-Ewen
Any tips appreciated!
Cheers!
Mark.
--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/f21096a9-7eee-46ad-8ad6-711e5a27d441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Thanks,
Ewen