Martin Krasser

@jypma we designed writes to Cassandra in a way that they always go to a single partition in order to avoid issues discussed in #48. With your addition, writes may...

@jypma I fully understand that waiting for #77 to be ready is in conflict with your project timelines. I'm willing to merge your contribution as a temporary solution to support...

@jypma ok, let's keep the PR open for now. Thanks anyway for your contribution. Regarding Java version, we should of course also target to 8+.

I won't upgrade to the new producer for reasons explained in https://github.com/RBMHTechnology/eventuate/issues/59. Briefly, the new producer doesn't support atomic writes of user-defined batches to a partition.

> it appears that the ordering is preserved @talp-traiana can you please point me to that location in the docs?

This is fine if there are no failures, but imagine the following situation: 4 events (e1, e2, e3 and e4) need to be written atomically. Internally, the producer adds e1...

@Fristi thanks for your investigations. What we'd need is the ability to make atomic batch writes to a single topic **partition**, it doesn't need to be transactional across partitions or...

> it seems that Java driver only supports send() method for producing single record, but in fact, the driver batches all records internally and sends them into Kafka in batches...

> I am interested to support this backend ... I will go deeply into Kafka Java driver and check if we can reuse some parts to implement producer or just...

> Finally, I was able to reuse some parts of Java driver and make batch requests - so I can confirm that we are able to implement producer which can...