The error message for too many element in a collection does not give keyspace or column family information. This makes it a pain point to try to determine which table is the offending table.
Example Error message:
Currently, to try to pinpoint the table in question. We need to trace all requests and then try to match up the timestamps in the CQL tracing session with the log timestamps to try and match. If prepared statements are used, this is a dead end due to the logged tracing information missing the query. In which case, we have to look at other 3rd party methods for capturing the queries to try and match up. This is extremely tedious when many tables have collections and a high number of ops against them.
Requesting that the error contain the keyspace.table name in the error message.