You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2015/04/06 18:46:17 UTC
[jira] [Updated] (GORA-378) Log error trace as well as error
message in GoraRecordWriter
[ https://issues.apache.org/jira/browse/GORA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney updated GORA-378:
--------------------------------------
Labels: memex (was: )
> Log error trace as well as error message in GoraRecordWriter
> ------------------------------------------------------------
>
> Key: GORA-378
> URL: https://issues.apache.org/jira/browse/GORA-378
> Project: Apache Gora
> Issue Type: Task
> Components: gora-core
> Affects Versions: 0.5
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Labels: memex
> Fix For: 0.6
>
>
> Right now I am logging a rather annoying error when attempting to flush Super Columns to Cassandra 2.0.7 which reads as follows
> 2014-09-26 20:43:15,847 WARN mapreduce.GoraRecordWriter - Exception at GoraRecordWriter.class while closing datastore.InvalidRequestException(why:supercolumn parameter is not optional for super CF sc)
> Yes, this is useful, however it would be better (for debugging purposes) if I could catch an entire stack trace as well within the log output.
> Patch coming up for GoraRecordWriter which does just this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)