[
https://issues.apache.org/jira/browse/GORA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150795#comment-14150795
]
Hudson commented on GORA-378:
-----------------------------
SUCCESS: Integrated in gora-trunk #1248 (See
[https://builds.apache.org/job/gora-trunk/1248/])
GORA-378 Log error trace as well as error message in GoraRecordWriter
(lewis.j.mcgibbney: rev 1a42a6239caf8f444a3c53ad7f86a6b681f7eccc)
*
gora-cassandra/src/main/java/org/apache/gora/cassandra/store/CassandraClient.java
* CHANGES.txt
* gora-core/src/main/java/org/apache/gora/mapreduce/GoraRecordWriter.java
> 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
> 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)
