Thanks for the information Tzu-Li. I will mock the FlinkKafkaProducer
class until this issue is fixed.
Timo
Am 05/10/16 um 17:57 schrieb Tzu-Li (Gordon) Tai:
Sorry, correction to my last statements:
On the consumer side I think the instantiation was already removed from the
constructor in a
Sorry, correction to my last statements:
On the consumer side I think the instantiation was already removed from the
constructor in a recent commit.
On October 5, 2016 at 11:37:41 PM, Tzu-Li (Gordon) Tai (tzuli...@apache.org)
wrote:
This matters on the consumer side, yes. Moving the
This matters on the consumer side, yes. Moving the instantiation out of the
constructor will require such
guarantee that the list fetched individually at subtasks are determinate and
identical.
On the producer side I don’t really think it matters. Unless the user
implementations of the
if you were to move the partition list fetching out of the constructor
int open(), is there any guarantee that for each fetching subtask the
partition list is identical?
On 05.10.2016 17:17, Tzu-Li (Gordon) Tai wrote:
Hi Timo,
I haven’t had the chance to look at the producer side too much
Hi Timo,
I haven’t had the chance to look at the producer side too much yet, but after a
look in the code,
I think it’s reasonable to remove the instantiation from the producer
constructor.
The instantiation in the constructor is only used for partition list fetching &
eager properties
Hey everyone,
I'm currently rewriting the KafkaTabeSinkTest and discovered something
that doesn't seem to be intended: Is it intended that
FlinkKafkaProducer08 cannot be instantiated without a running Kafka
instance?
The constructor of FlinkKafkaProducerBase calls getKafkaProducer() which
