[
https://issues.apache.org/jira/browse/CASSANDRA-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969376#comment-14969376
]
Paulo Motta commented on CASSANDRA-7645:
----------------------------------------
bq. Also, the fallback mechanism (show_session) uses the same
QueryTrace.populate mechanism to query the trace, but with a max_wait of 2.0
seconds.
actually only the fallback mechanism is not working, since the driver
[ignores|https://github.com/carlyeks/python-driver/blob/58536f57467db9998417eff57304ef40562f5975/cassandra/cluster.py#L1420]
the {{TraceUnavailable}} during {{ResultFuture}} construction.
maybe we should create a driver ticket to support partial query traces first?
> 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)
