Uploaded image for project: 'Apache Gora'
  1. Apache Gora
  2. GORA-169

Implement correct logging for KeySpaces and attributes in CassandraMappingManager

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.2.1
    • 0.3
    • gora-cassandra
    • None

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lewismc Lewis John McGibbney
            lewismc Lewis John McGibbney
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment