From commits-return-75953-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org Sun Jun 16 11:59:22 2013 Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4AF8910E39 for ; Sun, 16 Jun 2013 11:59:22 +0000 (UTC) Received: (qmail 28150 invoked by uid 500); 16 Jun 2013 11:59:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 27959 invoked by uid 500); 16 Jun 2013 11:59:21 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 27941 invoked by uid 99); 16 Jun 2013 11:59:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jun 2013 11:59:20 +0000 Date: Sun, 16 Jun 2013 11:59:20 +0000 (UTC) From: =?utf-8?Q?Micha=C5=82_Michalski_=28JIRA=29?= To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-5645) Display PK values along the header when using EXPAND in cqlsh MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5645?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13684630#comment-13684630 ]=20 Micha=C5=82 Michalski commented on CASSANDRA-5645: --------------------------------------------- After short investigation it seems that it could be very straightforward fi= x (getting and properly processing primary_key_components from CF layout) _= if_ we had KS and CF name accessible via cursor object. Unluckily - it seem= s we hadn't, so it's necessary to add them there (which, in general, doesn'= t seem to be a bad idea to me) - CqlResult seems to be a good place to star= t. However, I'd appreciate any suggestions. Maybe I missed something in exi= sting cursor implementation or is there better approach? =20 > 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=C5=82 Michalski > Assignee: Micha=C5=82 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 administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira