You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2013/12/28 05:34:51 UTC
[jira] [Commented] (HIVE-4257)
java.sql.SQLNonTransientConnectionException on JDBCStatsAggregator
[ https://issues.apache.org/jira/browse/HIVE-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857940#comment-13857940 ]
Ashutosh Chauhan commented on HIVE-4257:
----------------------------------------
[~teddy.choi] Would you like to rebase this patch on trunk? Lets have Hive QA run on this.
> java.sql.SQLNonTransientConnectionException on JDBCStatsAggregator
> ------------------------------------------------------------------
>
> Key: HIVE-4257
> URL: https://issues.apache.org/jira/browse/HIVE-4257
> Project: Hive
> Issue Type: Bug
> Components: Statistics
> Affects Versions: 0.11.0
> Reporter: Teddy Choi
> Assignee: Teddy Choi
> Priority: Minor
> Attachments: HIVE-4257.1.patch.txt
>
>
> java.sql.SQLNonTransientConnectionException occurs on JDBCStatsAggregator after executing dozens of Hive queries periodically, which inserts thousands of rows. It may have a relation with DERBY-5098. To avoid this error, Hive should use a more recent version of Derby(10.6.2.3, 10.7.1.4, 10.8.2.2, 10.9.1.0 or later). Hive 0.11.0-SNAPSHOT uses Derby 10.4.2.0.
> {noformat}
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator (JDBCStatsAggregator.java:aggregateStats(168)) - Error during publishing aggregation. java.sql.SQLNonTransientConnectionException: No current connection.
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator (JDBCStatsAggregator.java:aggregateStats(168)) - Error during publishing aggregation. java.sql.SQLNonTransientConnectionException: No current connection.
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator (JDBCStatsAggregator.java:cleanUp(249)) - Error during publishing aggregation. java.sql.SQLNonTransientConnectionException: No current connection.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)