[ https://issues.apache.org/jira/browse/CASSANDRA-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969398#comment-14969398
]
Adam Holmberg commented on CASSANDRA-7645:
------------------------------------------
bq. since the driver ignores the TraceUnavailable during ResultFuture construction.
That's why he originally changed it to attach the trace_id to the statement. That's also changing
in CASSANDRA-10513 and driver 3.0.
bq. maybe we should create a driver ticket to support partial query traces first?
Yes. I think QueryTrace should have the option to populate events without waiting for the
session.
https://datastax-oss.atlassian.net/browse/PYTHON-438
I defer on whether to reopen this ticket or create a new one.
> cqlsh: show partial trace if incomplete after max_trace_wait
> ------------------------------------------------------------
>
> Key: CASSANDRA-7645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7645
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Carl Yeksigian
> Priority: Trivial
> Fix For: 3.0.0 rc2, 2.2.4, 2.1.12
>
>
> If a trace hasn't completed within {{max_trace_wait}}, cqlsh will say the trace is unavailable
and not show anything. It (and the underlying python driver) determines when the trace is
complete by checking if the {{duration}} column in {{system_traces.sessions}} is non-null.
If {{duration}} is null but we still have some trace events when the timeout is hit, cqlsh
should print whatever trace events we have along with a warning about it being incomplete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|