RE: Kafka & Canary Release

2017-12-13 Thread Tauzell, Dave
@kafka.apache.org Cc: Zeevik Liak Subject: RE: Kafka & Canary Release No From: Yuval Alon Sent: Wednesday, 13 December 2017 10:52 To: users@kafka.apache.org<mailto:users@kafka.apache.org> Cc: Zeevik Liak mailto:zeevik.l...@amdocs.com>>; Assaf Katz mailto:assaf.k...@amdocs.com>&

RE: Kafka & Canary Release

2017-12-13 Thread Assaf Katz
No From: Yuval Alon Sent: Wednesday, 13 December 2017 10:52 To: users@kafka.apache.org Cc: Zeevik Liak ; Assaf Katz Subject: RE: Kafka & Canary Release Hi, Any reply on our last comment? Yuval Alon amdocs technology – Digital Mobile: +972-52-6148937 Office: +972-9-7789641 email:

RE: Kafka & Canary Release

2017-12-13 Thread Yuval Alon
k Liak ; Yuval Alon Subject: RE: Kafka & Canary Release Hi, It doesn’t so simple only micro service 1 knows about it - if micro service 2 send to micro service 1, it doesn’t have any idea that micro service 1 was updated. So we need to route it on message hub - Kafka. Thanks, Assaf From: Wim

RE: Kafka & Canary Release

2017-11-29 Thread Assaf Katz
: Wednesday, 29 November 2017 18:47 To: users@kafka.apache.org Cc: Assaf Katz ; Zeevik Liak Subject: Re: Kafka & Canary Release Isn't that simply a matter of changing your key to route the element to the right topic for 1 or the other microservice? -w On Wed, 29 Nov 2017 at 17:09 Y

Re: Kafka & Canary Release

2017-11-29 Thread Wim Van Leuven
Isn't that simply a matter of changing your key to route the element to the right topic for 1 or the other microservice? -w On Wed, 29 Nov 2017 at 17:09 Yuval Alon wrote: > Hello, > We are using Apache Kafka 0.10.2, which we understand is not supporting > “Canary Release

Kafka & Canary Release

2017-11-29 Thread Yuval Alon
Hello, We are using Apache Kafka 0.10.2, which we understand is not supporting “Canary Release” Is it in your pipeline, if so, when it’s going to be released? Explanation of the issue: We hold two different versions of micro services that subscrib