This seems really low risk to me. In order to be impacted, it'd have to be someone who was using the kafka integration in spark 2.0, which isn't even officially released yet.
On Mon, Jul 25, 2016 at 7:23 PM, Vahid S Hashemian <vahidhashem...@us.ibm.com> wrote: > Sorry, meant to ask if any Apache Sparkuser would be affected. > > --Vahid > > > > From: Vahid S Hashemian/Silicon Valley/IBM@IBMUS > To: user@spark.apache.org, d...@spark.apache.org > Date: 07/25/2016 05:21 PM > Subject: Potential Change in Kafka's Partition Assignment Semantics > when Subscription Changes > ________________________________ > > > > Hello, > > We have started a KIP under the Kafka project that proposes a fix for an > inconsistency in how partition assignments are currently handled in Kafka > when the consumer changes subscription. Note that this applies to new > consumer only. > The KIP can be found here: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-70%3A+Revise+Partition+Assignment+Semantics+on+New+Consumer%27s+Subscription+Change > > The compatibility section > (https://cwiki.apache.org/confluence/display/KAFKA/KIP-70%3A+Revise+Partition+Assignment+Semantics+on+New+Consumer%27s+Subscription+Change#KIP-70:RevisePartitionAssignmentSemanticsonNewConsumer'sSubscriptionChange-Compatibility,Deprecation,andMigrationPlan) > describes impacted users. > > We would like to know if any Apache Storm user would be affected by this > change. Thanks. > > Regards, > --Vahid > > --------------------------------------------------------------------- To unsubscribe e-mail: user-unsubscr...@spark.apache.org
