Don't assign trace data to Statements

Description

Depending on how a statement is executed (sync vs. async), sometimes trace data is transferred onto a Statement, sometimes not.

I don't think any request-specific results (trace information, warnings, custom payloads) should be attached to a statement. Instead, they should be kept associated with the ResponseFuture.

This task is to normalize handling of these data and update documentation.

It will require at least one update to cqlsh when trace_id is removed from Statement.

Environment

None

Pull Requests

None

Activity

Show:
Greg Bestland
October 21, 2015, 9:53 PM

Regression Complete

Michael Penick
October 20, 2015, 6:28 PM

+1 There's an unintentionally deleted space.

Adam Holmberg
October 14, 2015, 3:23 PM

cqlsh patch posted

Adam Holmberg
October 13, 2015, 5:24 PM

https://github.com/datastax/python-driver/pull/419

Built on PYTHON-368. Do that first

Adam Holmberg
October 13, 2015, 5:07 PM
Fixed

Assignee

Unassigned

Reporter

Adam Holmberg

Fix versions

Reviewer

Michael Penick