[
https://issues.apache.org/jira/browse/HIVE-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977849#comment-13977849
]
Amareshwari Sriramadasu commented on HIVE-6953:
-----------------------------------------------
The machine on which I'm running is a Linux machine. Same thing happens on Mac
as well.
{noformat}
uname -a
Linux <hostname> 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010
x86_64 GNU/Linux
$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
{noformat}
> 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
> Assignee: Alan Gates
> Attachments: nohup.out.gz
>
>
> 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)
