[
https://issues.apache.org/jira/browse/CASSANDRA-15905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147991#comment-17147991
]
Brandon Williams commented on CASSANDRA-15905:
----------------------------------------------
Sure, that'd be great. One thing I don't understand though, you say this only
happens on trunk, but CASSANDRA-11534 was fixed in 3.10.
> cqlsh not able to fetch all rows when in batch mode
> ---------------------------------------------------
>
> Key: CASSANDRA-15905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15905
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
> Reporter: Yifan Cai
> Priority: Normal
>
> The cqlsh in trunk only display the first page when running in the batch
> mode, i.e. using {{--execute}} or {{--file}} option.
>
> It is a change of behavior. In 3.x branches, the cqlsh returns all rows.
>
> It can be reproduced in 3 steps.
> {code:java}
> 1. ccm create trunk -v git:trunk -n1 && ccm start
> 2. tools/bin/cassandra-stress write n=1k -schema keyspace="keyspace1" //
> write 1000 rows
> 3. bin/cqlsh -e "SELECT * FROM keyspace1.standard1;" //
> fetch all rows
> {code}
>
> There are 1000 rows written. But the output in step 3 will only list 100
> rows, which is the first page.
> {code:java}
> ➜ bin/cqlsh -e "SELECT * FROM keyspace1.standard1" | wc -l
> 105{code}
>
> The related change was introduced in
> https://issues.apache.org/jira/browse/CASSANDRA-11534, where the cqlsh.py
> script no longer fetch all rows when not using tty in the print_result
> method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
