Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Nov 2015 21:26:11 +0000 (UTC)
From: "Carl Yeksigian (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12826579.1430498315000.165981.1448313971135@Atlassian.JIRA>
In-Reply-To: <JIRA.12826579.1430498315000@Atlassian.JIRA>
References: <JIRA.12826579.1430498315000@Atlassian.JIRA>
 <JIRA.12826579.1430498315321@arcas>
Subject: [jira] [Updated] (CASSANDRA-9286) Add Keyspace/Table details to
 CollectionType.java error message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian updated CASSANDRA-9286:
--------------------------------------
    Component/s: Observability

> 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: Observability
>            Reporter: sequoyha pelletier
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 2.0.15, 2.1.6
>
>         Attachments: 9286-2.0-v2.txt, 9286-2.0.txt, 9286-2.1-v2.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)