You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a batch of updates is created manually (e.g. in cqlsh), the full batch will be logged as one single audit record. However, if a prepared batch is executed, then individual records will be created for the different operations in the batch (and correlated with a batch id).
This behavior is not consistent and will confuse users. We should investigate if we can get separated batch entries always.
FWIW, the same behavior is present in Cassandra 4.0.
The text was updated successfully, but these errors were encountered:
When a batch of updates is created manually (e.g. in cqlsh), the full batch will be logged as one single audit record. However, if a prepared batch is executed, then individual records will be created for the different operations in the batch (and correlated with a batch id).
This behavior is not consistent and will confuse users. We should investigate if we can get separated batch entries always.
FWIW, the same behavior is present in Cassandra 4.0.
The text was updated successfully, but these errors were encountered: