[
https://issues.apache.org/jira/browse/CASSANDRA-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-18219:
---------------------------------------
Description:
The existing aggregation query warning messages in SelectStatement.java:
_'Aggregation query used without partition key'_
_'Aggregation query used on multiple partition keys (IN restriction)'_
are missing the helpful details which would assist users in quickly identifying
the offending query. The table name and type of aggregation would be useful
additions in the WARN message.
In addition, following the example of the slow query logger and printing out
the query at DEBUG level would be especially helpful.
was:
The existing aggregation query warning messages in SelectStatement.java:
_'Aggregation query used without partition key'_
_'Aggregation query used on multiple partition keys (IN restriction)'_
are missing the helpful details which would assist users in quickly identifying
the offending query. The table name and type of aggregation would be useful
additions in the WARN message.
In addition, following the example of the slow query logger and printing out
the query at DEBUG level would be especially helpful.
Today,
> Warning message on aggregation queries doesn't specify table name or
> aggregate type
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-18219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18219
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
> Reporter: Brad Schoening
> Priority: Normal
>
> The existing aggregation query warning messages in SelectStatement.java:
> _'Aggregation query used without partition key'_
> _'Aggregation query used on multiple partition keys (IN restriction)'_
> are missing the helpful details which would assist users in quickly
> identifying the offending query. The table name and type of aggregation would
> be useful additions in the WARN message.
> In addition, following the example of the slow query logger and printing out
> the query at DEBUG level would be especially helpful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
