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 9C8B018B9A for ; Wed, 16 Sep 2015 16:03:55 +0000 (UTC) Received: (qmail 60974 invoked by uid 500); 16 Sep 2015 16:03:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 60941 invoked by uid 500); 16 Sep 2015 16:03:46 -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 60926 invoked by uid 99); 16 Sep 2015 16:03:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 16:03:46 +0000 Date: Wed, 16 Sep 2015 16:03:45 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10350) cqlsh describe keyspace output no longers keeps indexes in sorted order MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790612#comment-14790612 ] Aleksey Yeschenko commented on CASSANDRA-10350: ----------------------------------------------- Most likely one the recent schema metadata changes. That said, it's not really a Major issue, if an issue at all. > cqlsh describe keyspace output no longers keeps indexes in sorted order > ----------------------------------------------------------------------- > > Key: CASSANDRA-10350 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10350 > Project: Cassandra > Issue Type: Bug > Reporter: Andrew Hust > Priority: Minor > Fix For: 3.0.x > > > cqlsh command {{describe keyspace }} no longer keeps indexes in alpha sorted order. This was caught with a dtest on [cassci|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_describe/]. > Tested on: C* {{b4544846def2bdd00ff841c7e3d9f2559620827b}} > Can be reproduced with the following: > {code} > ccm stop > ccm remove describe_order > ccm create -n 1 -v git:cassandra-2.2 describe_order > ccm start > cat << EOF | ccm node1 cqlsh > CREATE KEYSPACE ks1 WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1}; > USE ks1; > CREATE TABLE ks1.test (id int, col int, val text, val2 text, val3 text, PRIMARY KEY(id, col)); > CREATE INDEX ix0 ON ks1.test (col); > CREATE INDEX ix3 ON ks1.test (val3); > CREATE INDEX ix2 ON ks1.test (val2); > CREATE INDEX ix1 ON ks1.test (val); > DESCRIBE KEYSPACE ks1; > EOF > ccm stop > ccm setdir -v git:cassandra-3.0 > ccm start > sleep 15 > cat << EOF | ccm node1 cqlsh > DESCRIBE KEYSPACE ks1; > EOF > ccm stop > {code} > Ouput on <= cassandra-2.2: > {code} > CREATE INDEX ix0 ON ks1.test (col); > CREATE INDEX ix1 ON ks1.test (val); > CREATE INDEX ix2 ON ks1.test (val2); > CREATE INDEX ix3 ON ks1.test (val3); > {code} > Output on cassandra-3.0: > {code} > CREATE INDEX ix2 ON ks1.test (val2); > CREATE INDEX ix3 ON ks1.test (val3); > CREATE INDEX ix0 ON ks1.test (col); > CREATE INDEX ix1 ON ks1.test (val); > {code} > //CC [~enigmacurry] -- This message was sent by Atlassian JIRA (v6.3.4#6332)