Hi Jakub, I worked with trigger, I was auditing it by time . I considered the following partition keys for the audit table. 1. (timeuuid,uuid) OR, 2. formatted date in groups of 5 minutes 21 March 2015, 13:44:15 -> 201503211340
*Used it to batch operations by a group of minutes.* *Caution : If you have extremely heavy write/update work load, it may cause to create wide rows.* Your second point isn't clear. If you want the values of non primary key columns to be audited, as is done with triggers in MySQL, unfortunately, as far as I know, this can't be done. However for the values of partition key, clustering column, on which the update,insert,delete is called, this can be extracted by using the UnfilteredRowIterator of the Partition object you receive in the trigger function. Thanks and Regards, Siddharth Verma
