tvielgouarin edited a comment on issue #7405: [FLINK-11249] 
FlinkKafkaProducer011 can not be migrated to FlinkKafkaProducer
URL: https://github.com/apache/flink/pull/7405#issuecomment-458186468
 
 
   Hi @pnowojski, 
   I have managed to solve the recovery problem for the Kafka Broker. I have 
also implemented the test for the `FlinkKafkaProducer011` across different 
version of flink (1.7). So the result are the same for both 
`FlinkKakfaProducer` and `FlinkKafkaProducer011`. For both of them I'm trying 3 
different tests:
   
   1. ` testRestoreKafkaTempDirectory` check if we can recover the committed 
transaction --> OK
   2. `testRestorePendingTransaction`check if we can recover the pending 
transaction --> ERROR no pending transaction ( Not sure if this behaviour 
abnormal or just that we can't recover the pending transaction after a 
versioning )
   3. `testRestoreProducer` check if we can produce committed transaction and 
pending transaction after the versioning --> OK
   
   I have started to work on the last test FlinkKafkaProducer011 --> 
FlinkKafkaProducer : 
   But I'm quickly stuck with an exception when initializing the testHarness ( 
created with FlinkKafkaProducer ) with the savepoint of FlinkKakfaProducer011. 
Is this action feasible with the testHarness API or there is a turn around to 
this issue ?
   
   Refactoring should also be considered. However because I'm impacting on 
several directories : 
   - kafka-connector-base
   - kafka-connector-011
   - kafka-connector
   
   I'm not sure of the best ordering for now. I will think about it, but if you 
have suggestion feel free. 
   
   As always my code can be found here : 
https://github.com/tvielgouarin/flink/commits/FLINK-11249

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to