Dale Lane
Dale Lane
In theory, I think it's reasonable to do a subset to try and keep patch versions as cheap as possible. But in practice, other than the blog post, I don't...
I'll see if we have more luck with re-running the job quickly first
I don't think the problem is actually with the links being broken - the errors are all HTTP-429 - essentially GitHub complaining about too many requests coming too quickly.
I definitely see a lot of value in being able to group related server types together - and, for schema registries in particular, having a proper place to put these...
Another hack - one that I've used - is to use `oneOf` when describing a message, allowing me to describe all possible versions inside of that. I think rely on...
yes, that's true
@realmohan001 No - there isn't a dedicated place for it in the spec, although I have seen people embed it in the URL before as a workaround (e.g. `http://USERNAME:PASSWORD@schemaregistry-url` )...
> it is not working, because of the big secret value and its characters I'm not sure exactly what you mean by this, but it sounds like perhaps you forgot...
I'm still digesting all of this, so this isn't a very considered response from me. One initial thought jumped out at me though: **How do we represent distributed multi-broker systems...
> What would the code bindings do if I did something like this? I don't think that any of them are currently getting/setting headers based on the spec for Kafka...