Re: Upgrade path to 0.10.x

[Alexis Midon <al...@airbnb.com.INVALID>]

- This type of questions is pretty common on the ml. Personally I don't
think I could confidently described the compatibility/upgrade scenarios.
Some clarification is needed, ideally in a single place.

I think this is even more crucial as the number of new features increases
(which is exciting)

- Also would it make sense to release and version the clients independently
of the server? Afaik clients are tied to a protocol version, not a broker
version.

At the moment the "new consumer" is in beta but shipped with non beta
server code. Quite confusing.

Some clarity and predictability would be helpful.


On Thu, Mar 31, 2016 at 06:18 Tommy Becker <to...@tivo.com> wrote:

> Hey folks,
> We are currently still running Kafka 0.8.1.1, and are looking to upgrade.
> From what I have been able to tell, upgrading to 0.10.x will be supported
> from as far back as 0.8.2.x. But the documentation for 0.8.2.x seems to
> indicate that upgrading from 0.8.1.x effectively a no-op. So my question is
> does that imply that upgrading from 0.8.1.1 to 0.10.x will be supported?
>
> Regards,
> Tommy
>
>
> ________________________________
>
> This email and any attachments may contain confidential and privileged
> material for the sole use of the intended recipient. Any review, copying,
> or distribution of this email (or any attachments) by others is prohibited.
> If you are not the intended recipient, please contact the sender
> immediately and permanently delete this email and any attachments. No
> employee or agent of TiVo Inc. is authorized to conclude any binding
> agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo
> Inc. may only be made by a signed written agreement.
>

Re: Upgrade path to 0.10.x

[Guozhang Wang <wa...@gmail.com>]

There are some discussions in maintaining client compatibility across
broker versions, where the main idea is to allow clients to retrieve the
broker version programmatically (details in KIP-35).

As for now although clients and servers are released together they each can
be treated as different versions. For the new consumer released in 0.9, it
works with any 0.9 brokers as well as future released brokers as well. It
was tagged "beta" mainly because we want to leave it flexible for minor API
changes, but in any case it should work well with the servers.

Guozhang


On Sat, Apr 2, 2016 at 11:32 PM, Alexis Midon <
alexis.midon@airbnb.com.invalid> wrote:

> - This type of questions is pretty common on the ml. Personally I don't
> think I could confidently described the compatibility/upgrade scenarios.
> Some clarification is needed, ideally in a single place.
>
> I think this is even more crucial as the number of new features increases
> (which is exciting)
>
> - Also would it make sense to release and version the clients independently
> of the server? Afaik clients are tied to a protocol version, not a broker
> version.
>
> At the moment the "new consumer" is in beta but shipped with non beta
> server code. Quite confusing.
>
> Some clarity and predictability would be helpful.
>
>
> On Thu, Mar 31, 2016 at 06:18 Tommy Becker <to...@tivo.com> wrote:
>
> > Hey folks,
> > We are currently still running Kafka 0.8.1.1, and are looking to upgrade.
> > From what I have been able to tell, upgrading to 0.10.x will be supported
> > from as far back as 0.8.2.x. But the documentation for 0.8.2.x seems to
> > indicate that upgrading from 0.8.1.x effectively a no-op. So my question
> is
> > does that imply that upgrading from 0.8.1.1 to 0.10.x will be supported?
> >
> > Regards,
> > Tommy
> >
> >
> > ________________________________
> >
> > This email and any attachments may contain confidential and privileged
> > material for the sole use of the intended recipient. Any review, copying,
> > or distribution of this email (or any attachments) by others is
> prohibited.
> > If you are not the intended recipient, please contact the sender
> > immediately and permanently delete this email and any attachments. No
> > employee or agent of TiVo Inc. is authorized to conclude any binding
> > agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo
> > Inc. may only be made by a signed written agreement.
> >
>



-- 
-- Guozhang