[ 
https://issues.apache.org/jira/browse/CASSANDRA-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687091#comment-13687091
 ] 

Jonathan Ellis commented on CASSANDRA-5645:
-------------------------------------------

We definitely return KS/CF as part of the native protocol; is cqlsh still using 
Thrift?
                
> 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

Reply via email to