You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2014/04/22 15:24:19 UTC
[jira] [Commented] (HIVE-6953) All CompactorTest failing with
Table/View 'NEXT_TXN_ID' does not exist
[ https://issues.apache.org/jira/browse/HIVE-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976740#comment-13976740 ]
Amareshwari Sriramadasu commented on HIVE-6953:
-----------------------------------------------
There are no failures in trunk, all tests pass. [~rhbutani], do you think anything is missing in branch-0.13? Looking at commits, i couldnt figure out.
> All CompactorTest failing with Table/View 'NEXT_TXN_ID' does not exist
> ----------------------------------------------------------------------
>
> Key: HIVE-6953
> URL: https://issues.apache.org/jira/browse/HIVE-6953
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.13.0
> Reporter: Amareshwari Sriramadasu
>
> When I'm running all tests through the command 'mvn clean install -Phadoop-1', all CompactorTest classes TestInitiator, TestWorker, TestCleaner fail with following exception :
> {noformat}
> org.apache.hadoop.hive.metastore.api.MetaException: Unable to select from transaction database java.sql.SQLSyntaxErrorException: Table/View 'NEXT_TXN_ID' does not exist.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> ....
> Caused by: java.sql.SQLException: Table/View 'NEXT_TXN_ID' does not exist.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
> {noformat}
> This is happening on branch-0.13. Has anyone faced this problem?
> [~owen.omalley] or someone else help me solve this. Do i have to set anything?
--
This message was sent by Atlassian JIRA
(v6.2#6252)