Lewis John McGibbney created GORA-169:
-----------------------------------------

             Summary: Implement correct logging for KepSpaces and attributes in 
CassandraMappingManager
                 Key: GORA-169
                 URL: https://issues.apache.org/jira/browse/GORA-169
             Project: Apache Gora
          Issue Type: Improvement
          Components: storage-cassandra
    Affects Versions: 0.2.1
            Reporter: Lewis John McGibbney
             Fix For: 0.3


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

{code}
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'
{code}

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: 

{code}
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
{code}

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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to