Thanks Robert,
In RDBMS select count(1) basically returns the rows.
1> select count(1) from t
2> go
-----------
300000
(1 row affected)
Is count(1) fundamentally different in Cassandra?
Does count(1) means return (in my case) 1 three hundred thousand time?
Cheers,
Mich Talebzadeh
http://talebzadehmich.wordpress.com
Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7.
co-author "Sybase Transact SQL Guidelines Best Practices", ISBN
978-0-9759693-0-4
Publications due shortly:
Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
Coherence Cache
Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
From: Robert Wille [mailto:[email protected]]
Sent: 22 April 2015 14:44
To: [email protected]
Subject: Re: OperationTimedOut in selerct count statement in cqlsh
Keep in mind that "select count(l)" and "select l" amount to essentially the
same thing.
On Apr 22, 2015, at 3:41 AM, Tommy Stendahl <[email protected]>
wrote:
Hi,
Checkout CASSANDRA-8899, my guess is that you have to increase the timeout
in cqlsh.
/Tommy
On 2015-04-22 11:15, Mich Talebzadeh wrote:
Hi,
I have a table of 300,000 rows.
When I try to do a simple
cqlsh:ase> select count(1) from t;
OperationTimedOut: errors={}, last_host=127.0.0.1
Appreciate any feedback
Thanks,
Mich
NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.
