Re: How to migrate Kafka Producer ?

[Piotr Nowojski <pi...@data-artisans.com>]

Hi Edward,

Sorry for coming back so late (because of holiday season).

You are unfortunately right. Our FlinkKafkaProducer should have been upgrade-able, but it is not. I have created a bug for this [1]. For the time being, until we fix the issue, you should be able to stick to 0.11 producer without noticeable negative effects. Our FlinkKafkaProducer011 has the same forward & backward compatibility as the universal FlinkKakfaProducer (The biggest change between two of them was just changing the naming convention), so you can use either of them with the same versions of Kafka brokers (0.10+).

Piotrek

[1] https://issues.apache.org/jira/browse/FLINK-11249

> On 18 Dec 2018, at 14:33, Edward Rojas <ed...@gmail.com> wrote:
> 
> Hi,
> 
> I'm planning to migrate from kafka connector 0.11 to the new universal kafka
> connector 1.0.0+ but I'm having some troubles.
> 
> The kafka consumer seems to be compatible but when trying to migrate the
> kafka producer I get an incompatibility error for the state migration. 
> It looks like the producer uses a list state of type
> "NextTransactionalIdHint", but this class is specific for each Producer
> (FlinkKafkaProducer011.NextTransactionalIdHint  vs
> FlinkKafkaProducer.NextTransactionalIdHint) and therefore the states are not
> compatible.
> 
> 
> I would like to know what is the recommended way to perform this kind of
> migration without losing the state ?
> 
> Thanks in advance,
> Edward
> 
> 
> 
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: How to migrate Kafka Producer ?

[Edward Rojas <ed...@gmail.com>]

Hi Piotr,

Thank you for looking into this. 
Do you have an idea when next version (1.7.2) will be available ?

Also, could you validate / invalidate the approach I proposed in the
previous comment ?


Edward Rojas wrote
> Regarding the kafka producer I am just updating the job with the new
> connector and removing the previous one and upgrading the job by using a
> savepoint and the --allowNonRestoredState. 
> So far my tests with this option are successful.

Is there any risk of using this approach and just ignore the state of the
previous Producer ?


Thanks again for your help.

Edward



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/