Thanks! That buys me some time from having to fork ZookeeperNetEx and do a 3.5.x port myself. Additionally, it should allow me to use Kafka with a 3.5.x zookeeper.
-- Kathryn Hogg Senior Technology Architect -----Original Message----- From: Andor Molnar [mailto:[email protected]] Sent: Thursday, September 5, 2019 12:42 AM To: [email protected] Subject: Re: Migrate from 3.4.x to 3.5.5 {External email message: This email is from an external source. Please exercise caution prior to opening attachments, clicking on links, or providing any sensitive information.} Hi Kathryn, That way should work without problems. Andor -----Original Message----- From: Kathryn Hogg <[email protected]> Reply-To: [email protected] To: [email protected] <[email protected]> Subject: RE: Migrate from 3.4.x to 3.5.5 Date: Wed, 4 Sep 2019 15:07:11 +0000 Question about the opposite: We have some C# clients using ZookeeperNetEx which hasn't released a 3.5 version yet. Will 3.4 clients work with 3.5 servers? --Kathryn HoggSenior Technology Architect -----Original Message-----From: Andor Molnar [mailto:[email protected]] Sent: Wednesday, September 4, 2019 9:52 AMTo: [email protected] Subject: Re: Migrate from 3.4.x to 3.5.5 {External email message: This email is from an external source. Please exercise caution prior to opening attachments, clicking on links, or providing any sensitive information.} Hi Zili, "If so, it seems upgrade client side force user to upgrade server side also.” Yes, if client is upgraded _and_ user wants to use a new feature in 3.5, then server side has to be upgraded too. ;) Andor > On 2019. Sep 3., at 13:20, Zili Chen <[email protected]> wrote: > If so, it seems upgrade client side force user to upgrade server side > also.
