[ 
https://issues.apache.org/jira/browse/CASSANDRA-9286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531243#comment-14531243
 ] 

Tyler Hobbs commented on CASSANDRA-9286:
----------------------------------------

Can you add a unit test for this, at least in 2.1 (with CqlTester)?  There's an 
{{assertInvalidMessage()}} method that you can use to check error message 
contents.

> Add Keyspace/Table details to CollectionType.java error message
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-9286
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9286
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sequoyha pelletier
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 2.1.x, 2.0.x
>
>         Attachments: 9286-2.0.txt, 9286-2.1.txt
>
>
> 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:
> {noformat}
> ERROR [Native-Transport-Requests:809453] 2015-04-23 22:48:21,189 
> CollectionType.java (line 116) Detected collection with 136234 elements, more 
> than the 65535 limit. Only the first 65535 elements will be returned to the 
> client. Please see http://cassandra.apache.org/doc/cql3/CQL.html#collections 
> for more details.
> {noformat}
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to