Ewen Cheslack-Postava

@mbonaci Oops, for some reason it didn't include the link. It is here: http://clabot.confluent.io/cla I think the only problem with this patch is that docker-machine still seems to be in...

@markrendle This looks like a limitation in docker-compose. See https://docs.docker.com/compose/faq/#how-do-i-get-compose-to-wait-for-my-database-to-be-ready-before-starting-my-application What's happening (based on how I saw it run locally) is that the schema-registry is being started up before other...

Works in conjunction with https://github.com/confluentinc/rest-utils/pull/90 and avoids `Address already in use` errors during tests due to `choosePort` not being a reliable way to select a random available port.

`batch.size` is best effort for each set of records delivered to the sink connector: ``` Specifies how many records to attempt to batch together for insertion into the destination table,...

@ronaklotia Yes, you'd need to create those files. They would contain the [avro schemas](https://avro.apache.org/docs/1.8.1/spec.html#schemas) for your key and value. There is also a `loads(schema)` function that loads it from a...

@kjvalencik This is a parameter that the normal Java clients actually enforce and refuse to return data if it exceeds the configured size. In fact, brokers are also supposed to...

@asasvari I was trying to get a clean system test build, but haven't been able to so far. Here's the report from a recent run: http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2018-02-23--001.1519386952--asasvari--KAFKA-6332--b40a9f3/report.html Some of them look...

@asasvari The problem with using the `jmx_port` is that it may be opened significantly before the port(s) that Kafka listens on just due to the order in which things run....

@ijuma not really, it has just been sitting in my review backlog until I find time to revisit the final changes

We need to be careful about compatibility here (no pun intended). We should leave the `compatibilityLevel` field in, fix it to include `compatibility`, and updated the docs to clarify that...