Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <27100254.161741295890964410.JavaMail.jira@thor>
Date: Mon, 24 Jan 2011 12:42:44 -0500 (EST)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-2028) Cassandra should log, at info
 level, when a keyspace and/or column family is created and/or updated
In-Reply-To: <9943959.116861295647665570.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek updated CASSANDRA-2028:
-------------------------------------

    Attachment: v1-0001-log-migration-details-at-INFO.txt

> Cassandra should log, at info level, when a keyspace and/or column family is created and/or updated
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2028
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2028
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Matthew F. Dennis
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.1
>
>         Attachments: v1-0001-log-migration-details-at-INFO.txt
>
>
> Cassandra currently doesn't log at info level when schema changes happen.  It should probably log details about what is being created/changed when it applies the changes locally.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.