[
https://issues.apache.org/jira/browse/GORA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated GORA-95:
-------------------------------------
Attachment: GORA-95-v2.patch
This patch improves logging for Cassandra mapping. It does LOG.info when things
are going well and LOG.warn to catch when we don't get some correct mappings. I
don't think this covers 'all' possible logging in cassandra mapping but goes
some lengths to smartening it up. Please feel free to add some other logging if
necessary.
> Catch incorrect mapping configurations and implement sufficient logging.
> ------------------------------------------------------------------------
>
> Key: GORA-95
> URL: https://issues.apache.org/jira/browse/GORA-95
> Project: Apache Gora
> Issue Type: Improvement
> Components: storage-cassandra, testing
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Fix For: 0.3
>
> Attachments: GORA-95-v2.patch, GORA-95.patch
>
>
> Whilst (pulling my hair out) writing the cassandra test suite, after many
> failing tests and some debugging I noticed that, under many
> InvocationTargetException's, CassandraMapping#loadConfiguration() throws the
> following
> Caused by: java.lang.NullPointerException
> at
> org.apache.gora.cassandra.store.CassandraMapping.loadConfiguration(CassandraMapping.java:100)
> at
> org.apache.gora.cassandra.store.CassandraClient.init(CassandraClient.java:66)
> at
> org.apache.gora.cassandra.store.CassandraStore.<init>(CassandraStore.java:72)
> ... 43 more
> when it cannot load the correct configuration from gora.properties. I know it
> is not great practice to put the while method in a try catch block so would
> be good to work towards a better solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
