[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297181#comment-14297181
]
Tyler Hobbs commented on CASSANDRA-8012:
I believe many of the failures mentioned here can be explained by
CASSANDRA-8512. Mixed-version clusters will normally have schema
disagreements, which was causing cqlsh to be unable to execute DESCRIBE
commands and SELECT statements.
However, I don't think this explains your problem, [~rfurmanski]. Can you (or
[~yangzhe1991] or [~CRolo]) try applying the patch on CASSANDRA-8512 by running
patch -p1 8512-2.1.txt from the top-level cassandra directory and see if it
happens to resolve the issue for you?
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Priority: Minor
Labels: cqlsh
Fix For: 2.1.3
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296797#comment-14296797
]
Carlos Rolo commented on CASSANDRA-8012:
Just to know if this is related or should I open a new ticket.
On Cassandra 2.1.2 cqlsh is I open a shell in a server while another server is
joining the cluster (In my case was on a different DC even) if I do any DESC
statement I get an empty result or on SELECT statements that the table doesn't
exist. Even after the server is fully joined and with all the data it still
keeps throwing the error. Only after I logout and login again in the cqlsh It
gets back to normal.
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Priority: Minor
Labels: cqlsh
Fix For: 2.1.3
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290508#comment-14290508
]
Phil Yang commented on CASSANDRA-8012:
--
I have the same issue, and even more, sometimes I can not select any data.
{noformat}
cqlsh desc keyspaces;
empty
cqlsh SELECT * FROM system.schema_keyspaces;
Traceback (most recent call last):
File /apache-cassandra-2.1.1/bin/cqlsh, line 861, in onecmd
self.handle_statement(st, statementtext)
File /apache-cassandra-2.1.1/bin/cqlsh, line 899, in handle_statement
return custom_handler(parsed)
File /apache-cassandra-2.1.1/bin/cqlsh, line 930, in do_select
self.perform_statement(statement)
File /apache-cassandra-2.1.1/bin/cqlsh, line 935, in perform_statement
result = self.perform_simple_statement(stmt)
File /apache-cassandra-2.1.1/bin/cqlsh, line 968, in
perform_simple_statement
self.print_result(rows, self.parse_for_table_meta(statement.query_string))
File /apache-cassandra-2.1.1/bin/cqlsh, line 949, in parse_for_table_meta
return self.get_table_meta(ks, cf)
File /apache-cassandra-2.1.1/bin/cqlsh, line 714, in get_table_meta
ksmeta = self.get_keyspace_meta(ksname)
File /apache-cassandra-2.1.1/bin/cqlsh, line 699, in get_keyspace_meta
raise KeyspaceNotFound('Keyspace %r not found.' % ksname)
KeyspaceNotFound: Keyspace 'system' not found.
cqlsh use system;
cqlsh:system
cqlsh:system use system2;
code=2200 [Invalid query] message=Keyspace 'system2' does not exist
cqlsh:system
{noformat}
I can change the keyspace by use and it can judge whether this keyspace is
exist.
And if I use 2.0.6's cqlsh to connect 2.1.1 cluster, it will work without any
error at all.
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Priority: Minor
Labels: cqlsh
Fix For: 2.1.3
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14207860#comment-14207860
]
Rafał Furmański commented on CASSANDRA-8012:
I have exact same issue in cassandra v. 2.1.1
{code}
root@db1:~# cqlsh 10.210.3.221 --debug
Using CQL driver: module 'cassandra' from
'/usr/share/cassandra/lib/cassandra-driver-internal-only-2.1.1.post.zip/cassandra-driver-2.1.1.post/cassandra/__init__.py'
Connected to Production Cluster at 10.210.3.221:9042.
[cqlsh 5.0.1 | Cassandra 2.1.1 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh DESCRIBE keyspaces;
empty
cqlsh DESCRIBE keyspace sync;
Traceback (most recent call last):
File /usr/bin/cqlsh, line 861, in onecmd
self.handle_statement(st, statementtext)
File /usr/bin/cqlsh, line 899, in handle_statement
return custom_handler(parsed)
File /usr/bin/cqlsh, line 1265, in do_describe
self.describe_keyspace(ksname)
File /usr/bin/cqlsh, line 1137, in describe_keyspace
self.print_recreate_keyspace(self.get_keyspace_meta(ksname), sys.stdout)
File /usr/bin/cqlsh, line 699, in get_keyspace_meta
raise KeyspaceNotFound('Keyspace %r not found.' % ksname)
KeyspaceNotFound: Keyspace 'sync' not found.
cqlsh use sync;
cqlsh:sync
{code}
Any ideas how to fix this? Attaching cluster info:
{code}
root@db1:~# nodetool describecluster
Cluster Information:
Name: Production Cluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
f8040381-4d5b-38da-9eda-5fd96474694a: [10.210.3.160,
10.210.3.224, 10.210.3.221, 10.195.15.163, 10.195.15.162]
{code}
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Priority: Minor
Labels: cqlsh
Fix For: 2.1.3
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181345#comment-14181345
]
Deives Michellis commented on CASSANDRA-8012:
-
I think it is worth mentioning it here...
Once I bumped the whole cluster to 2.1.0, this issue went away.
(It was a test VM cluster with 5 nodes and about 700k of actual data per node,
so YMMV with bigger datasets)
I will do this upgrade on a larger, multi-dc cluster with slightly more data
(about 50Tb in total) and will post the results :)
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181407#comment-14181407
]
Deives Michellis commented on CASSANDRA-8012:
-
Upgraded the cluster, and it started working properly on cqlsh after nodetool
upgradesstables have been running for a few mins (got past the system tables,
would be my guess)
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180120#comment-14180120
]
Serge Balyuk commented on CASSANDRA-8012:
-
I've witnessed similar issue. After upgrading one node from 2.0.8 to 2.1.0,
cqlsh on that node was behaving as described above. At the same time,
{{nodetool describecluster}} showed different schema versions for the upgraded
node and the rest of nodes in cluster. After the first attempt at {{nodetool
resetlocalschema}}, the node's schema version changed but it was still
different from cluster's common schema version. Subsequent attempts at
{{resetlocalchema}} had no effect. After restarting upgraded node {{nodetool
describecluster}} on it showed {{UNREACHABLE}} for all nodes except itself.
boot.log had many exceptions similar to this:
{code}
WARN o.a.c.net.IncomingTcpConnection - UnknownColumnFamilyException reading
from socket; closing org.apache.cassandra.db.UnknownColumnFamilyException:
Couldn't find cfId=.
DEBUG o.a.cassandra.net.MessagingService - Reseting version for /A.B.C.D
{code}
At the same time {{nodetool status}} shows {{UN}} for all nodes from both
upgraded node and old nodes.
Had to fallback to upgrading to 2.0.10. After removing all incompatible
sstables which 2.1.0 created during its uptime, {{describecluster}} shows
single version for all nodes, cqlsh performs as expected on
upgraded-then-downgraded node.
As noted in CASSANDRA-8023 this issue may be not just a tools issue unless I've
missed some important step in 2.0.x - 2.1.0 upgrade procedure.
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Assignee: Tyler Hobbs
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157232#comment-14157232
]
Shawn Zhou commented on CASSANDRA-8012:
---
Here is the result:
cqlsh SELECT * FROM system.schema_keyspaces;
keyspace_name | durable_writes | strategy_class
| strategy_options
-++--+
as_id_store | True |
org.apache.cassandra.locator.NetworkTopologyStrategy |
{DC2:2,DC1:2}
as_user_segment | True |
org.apache.cassandra.locator.NetworkTopologyStrategy |
{DC2:2,DC1:2}
as_user_fact | True |
org.apache.cassandra.locator.NetworkTopologyStrategy |
{DC2:0,DC1:2}
OpsCenter | True |
org.apache.cassandra.locator.SimpleStrategy | {replication_factor:2}
system | True |
org.apache.cassandra.locator.LocalStrategy | {}
system_traces | True |
org.apache.cassandra.locator.SimpleStrategy | {replication_factor:2}
(6 rows)
cqlsh SELECT * FROM system.schema_columnfamilies;
keyspace_name | columnfamily_name | bloom_filter_fp_chance | caching
| cf_id|
column_aliases | comment
| compaction_strategy_class
| compaction_strategy_options | comparator
| compression_parameters
| default_time_to_live | default_validator
| dropped_columns | gc_grace_seconds | index_interval |
is_dense | key_aliases| key_validator
|
local_read_repair_chance | max_compaction_threshold | max_index_interval |
memtable_flush_period_in_ms | min_compaction_threshold | min_index_interval |
read_repair_chance | speculative_retry | subcomparator | type | value_alias
-+---++-+--+--+--+-+--+--+--+--+---+-+--++--+++--+--++-+--+++---+---+--+-
as_id_store | foreign_id_to_netid_store |0.1 |
{keys:ALL, rows_per_partition:NONE} |
aaefa7d7-9d72-3d18-b5f0-02b30cee5bd7 |[type_from] |
|
org.apache.cassandra.db.compaction.LeveledCompactionStrategy |
{sstable_size_in_mb:256} |
org.apache.cassandra.db.marshal.UTF8Type |
{sstable_compression:org.apache.cassandra.io.compress.LZ4Compressor} |
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157233#comment-14157233
]
Shawn Zhou commented on CASSANDRA-8012:
---
With the bugs in 2.1 you know now, would you say it is production ready and
advise us to upgrade to 2.1 in production?
Could give me a list of most serious bugs in 2.1?
Thanks,
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157307#comment-14157307
]
Tyler Hobbs commented on CASSANDRA-8012:
Thanks, let me see if I can figure out what's going on.
bq. With the bugs in 2.1 you know now, would you say it is production ready and
advise us to upgrade to 2.1 in production?
It is generally not advised to upgrade to an {{x.y.0}} version for production
at all, unless there is a very good reason for doing so.
bq. Could give me a list of most serious bugs in 2.1?
I cannot, but you can find a list of tickets that have already been fixed for
2.1.1 or may be fixed for 2.1.1 with a search like this:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%202.1.1.
Note that many of those tickets were committed prior to the release of 2.1.0
(but were not included in 2.1.0).
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155342#comment-14155342
]
Tyler Hobbs commented on CASSANDRA-8012:
[~shawnzhou] sorry for the slow response. Can you paste the output of the
following queries?
{noformat}
SELECT * FROM system.schema_keyspaces;
SELECT * FROM system.schema_columnfamilies;
SELECT * FROM system.schema_columns;
{noformat}
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
Labels: cqlsh
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149943#comment-14149943
]
Tyler Hobbs commented on CASSANDRA-8012:
[~shawnzhou] can you start cqlsh with the {{--debug}} flag and see if
{{DESCRIBE KEYSPACES}} produces an error?
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8012) cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149953#comment-14149953
]
Shawn Zhou commented on CASSANDRA-8012:
---
Did not see any error
[root@dc1-stg-cassandra-08 lib]# cqlsh dc1-stg-cassandra-08.dc01.revsci.net -k
as_user_segment --debug
Using CQL driver: module 'cassandra' from
'/usr/share/cassandra/lib/cassandra-driver-internal-only-2.1.0.post.zip/cassandra-driver-2.1.0.post/cassandra/__init__.py'
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
cqlsh:as_user_segment exit
cqlsh DESCRIBE KEYSPACES; returns empty after upgrade
---
Key: CASSANDRA-8012
URL: https://issues.apache.org/jira/browse/CASSANDRA-8012
Project: Cassandra
Issue Type: Bug
Components: Tools
Environment: cassandra 2.1.0
Reporter: Shawn Zhou
after upgrade from 2.0.7 to 2.1.0
run cqlsh DESCRIBE KEYSPACES; returns empty result;
query individual table does return data;
See below:
{noformat}
[root@dc1-stg-cassandra-08 cassandra]# cqlsh
dc1-stg-cassandra-08.dc01.revsci.net -k as_user_segment
Connected to Stage Cluster at dc1-stg-cassandra-08.dc01.revsci.net:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh:as_user_segment DESCRIBE KEYSPACES;
empty
cqlsh:as_user_segment select * from user_segments_blob where id =
'8e6090087fc1a7591a99dc4cb744ac43';
id | segments
--+
8e6090087fc1a7591a99dc4cb744ac43 |
0x9416b015911d3b0e211aee227216ab1cdf0f4204
(1 rows)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
