[
https://issues.apache.org/jira/browse/CASSANDRA-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687654#comment-13687654
]
Michał Michalski commented on CASSANDRA-5645:
---------------------------------------------
Yes - it even tells so when it starts and the only transport available in
pylib/cqlshlib is the Thrift one.
Moreover, while python-cql seems to support native protocol, cqlsh doesn't make
any use of it - it even contains some methods like
"make_hacktastic_thrift_call" which makes me think it's currently quite
Thrift-dependent ;-)
> Display PK values along the header when using EXPAND in cqlsh
> -------------------------------------------------------------
>
> Key: CASSANDRA-5645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5645
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Michał Michalski
> Assignee: Michał Michalski
> Priority: Minor
>
> Follow-up to CASSANDRA-5597 proposed by [~jjordan].
> Currently cqlsh run in vertical mode prints a header like this:
> {noformat}cqlsh> EXPAND on;
> Now printing expanded output
> cqlsh> SELECT * FROM system.schema_columnfamilies limit 1;
> @ Row 1
> -----------------------------+-----------------------------------------------------------------------------------------
> keyspace_name | system_auth
> columnfamily_name | users
> bloom_filter_fp_chance | 0.01
> caching | KEYS_ONLY
> column_aliases | []
> (...){noformat}
> The idea is to make it print header this way:
> {noformat}cqlsh> EXPAND on;
> Now printing expanded output
> cqlsh> SELECT * FROM system.schema_columnfamilies limit 1;
> @ Row 1: system_auth, users
> -----------------------------+-----------------------------------------------------------------------------------------
> keyspace_name | system_auth
> columnfamily_name | users
> bloom_filter_fp_chance | 0.01
> caching | KEYS_ONLY
> column_aliases | []
> (...){noformat}
> [~jjordan], please verify if it's what you requested for.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
