[GORA-169] Implement correct logging for KeySpaces and attributes in CassandraMappingManager

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2.1
• Fix Version/s: 0.3
• Component/s: gora-cassandra
• Assignee: Lewis John McGibbney
• Reporter: Lewis John McGibbney
• Created: 20/Sep/12 23:37
• Updated: 01/Jul/13 05:05
• Resolved: 09/Feb/13 21:12

Description

Currently the logging in CassandraMappingManager#loadConfiguration() fails to pick up a wealth of information from the keyspace definitions. An example is below:

2012-09-20 23:47:05,469 INFO  store.CassandraMappingManager - Located Cassandra Keyspace: 'keyspace'
2012-09-20 23:47:05,476 INFO  store.CassandraMappingManager - Located Cassandra Keyspace name: 'name'
2012-09-20 23:47:05,476 INFO  store.CassandraMappingManager - Located Cassandra Mapping: 'class'
2012-09-20 23:47:05,476 INFO  store.CassandraMappingManager - Located Cassandra Mapping class name: 'name'

As the logging incorrectly uses the jdom methods, keyspace names and additional logging is incorrect and not nearly enough of what should be present. It should be changed to reflect below:

2012-09-20 23:47:05,476 INFO  store.CassandraMappingManager - Located Cassandra Keyspace name: '$nameOfKeySpace'
2012-09-20 23:47:05,476 INFO  store.CassandraMappingManager - Located Cassandra Mapping for class: '$nameOfMappingClass'
...
etc

right now this is very misleading and needs to be sorted out with much more verbose logging for keyspace & attribute recognition.

Issue Links

• is related to: GORA-203 Bug in setting column field attribute "qualifier" in CassandraMapping