Github user Bekreth commented on the issue:
    What I was hoping to achieve was a CassandraSink that could write objects 
as single statements, or in a batch statement.  This would allow for minor 
transaction protection, guarenteeing a group of elements are all successfully 
written together.  However, it seems clear to me that I missed the forest for 
the trees on this one.  Looking over the `SinkFunction`, its clear to me the 
only way this functionality could be added would be to overload the `invoke` 
method on the `@Public` interface.  


Reply via email to