[
https://issues.apache.org/jira/browse/CASSANDRA-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992786#comment-13992786
]
Jeremiah Jordan commented on CASSANDRA-7192:
--------------------------------------------
My guess is this probably belongs in the Java Driver JIRA:
https://datastax-oss.atlassian.net/browse/JAVA
Unless there is a server side bug with tracing and paging interacting, but I'm
guessing this is probably just having to do with how the java driver queries
the information.
> QueryTrace for a paginated query exists only for the first element of the
> list returned by getAllExecutionInfo()
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7192
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7192
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: A Cassandra 2.0.6 cluster of 16 nodes running on Ubuntu
> 12.04.2 LTS, using the Java Driver in the client.
> Reporter: Roger Hernandez
> Priority: Minor
>
> Within the Java Driver, with tracing enabled, I execute a large query that
> benefits from automatic pagination (with fetchSize=10).
> I make sure to go through all of the ResultSet, and by the end of the query I
> call getAllExecutionInfo() on the ResultSet. This returns an ArrayList of 9
> ExecutionInfo elements (the number of pages it requested from Cassandra).
> When accessing the QueryTrace in the ExecutionInfo from the ArrayList at
> index 0, I can retrieve the information without issues. However, the first is
> the only one that has QueryTrace information, every other ExecutionInfo of
> the array returns a NULL QueryTrace object.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
