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

Brad Schoening updated CASSANDRA-20099:
---------------------------------------
    Description: 
When paging is used, the trace is repeated multiple times.  For example,
{quote}> PAGING 2

> TRACING ON

> select * from system_schema.columns LIMIT 10;
{quote}
Also, for consistency with the other ON/OFF flags used with Paging, , the 
TRACING message should be updated as below.  This could work well if it *used 
on_off_switch_with_value,* but it only has OFF & Value and would need to be 
tweaked.
 * Capture is ON, writing to '/tmp/output'
 * Capture set to OFF
 * Capture is OFF

  was:
When paging is used, the trace is repeated multiple times.  For example,
{quote}> PAGING 2

> TRACING ON

> select * from system_schema.columns LIMIT 10;
{quote}


> Fix TRACING when PAGING so it doesn't repeat the tracing multiple times
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-20099
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20099
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Interpreter
>            Reporter: Brad Schoening
>            Priority: Low
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 5.1
>
>
> When paging is used, the trace is repeated multiple times.  For example,
> {quote}> PAGING 2
> > TRACING ON
> > select * from system_schema.columns LIMIT 10;
> {quote}
> Also, for consistency with the other ON/OFF flags used with Paging, , the 
> TRACING message should be updated as below.  This could work well if it *used 
> on_off_switch_with_value,* but it only has OFF & Value and would need to be 
> tweaked.
>  * Capture is ON, writing to '/tmp/output'
>  * Capture set to OFF
>  * Capture is OFF



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to