I’m Alexander from Confluent. I am new to Flink and its community. I would
like to contribute to the Flink Table Store, but am missing certain
details. Can someone please clarify the points mentioned below to me?

   - Given that there is always a single writer to a stream, in what
   situations can concurrent writes ever happen to Flink Table Store? FLIP-188
   mentions reprocessing and snapshot generation, but I do not understand how
   these cases can lead to more than a single writer.
   - If there are concurrent INSERTs into a table baked by Flink Table
   Store, how and by what component are they serialized?
   - Is Flink Table Store going to support ACID transactions?
   - Do Flink Table Store snapshots correspond 1:1 to Flink checkpoints?
   - Does Flink Table Store (plan to) support secondary indexes?
   - Is there an open roadmap for this Flink Table Store?

Thank you,
Alexander

Reply via email to