You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2011/01/21 23:07:45 UTC
[jira] Created: (CASSANDRA-2028) Cassandra should log, at info
level, when a keyspace and/or column family is created and/or updated
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: Improvement
Affects Versions: 0.7.0
Reporter: Matthew F. Dennis
Priority: Minor
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.
[jira] Updated: (CASSANDRA-2028) Cassandra should log, at info
level, when a keyspace and/or column family is created and/or updated
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2028:
--------------------------------------
Component/s: Core
Affects Version/s: (was: 0.7.0)
0.7 beta 1
Fix Version/s: 0.7.1
Assignee: Gary Dusbabek
Issue Type: Wish (was: Improvement)
> 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
>
>
> 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.
[jira] Commented: (CASSANDRA-2028) Cassandra should log, at info
level, when a keyspace and/or column family is created and/or updated
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985884#action_12985884 ]
Hudson commented on CASSANDRA-2028:
-----------------------------------
Integrated in Cassandra-0.7 #198 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/198/])
log migrations at INFO. patch by gdusbabek, reviewed by jbellis. CASSANDRA-2028
> 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.
[jira] Commented: (CASSANDRA-2028) Cassandra should log, at info
level, when a keyspace and/or column family is created and/or updated
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985848#action_12985848 ]
Jonathan Ellis commented on CASSANDRA-2028:
-------------------------------------------
+1
> 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.
[jira] Updated: (CASSANDRA-2028) Cassandra should log, at info
level, when a keyspace and/or column family is created and/or updated
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ 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.