You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2016/05/07 16:30:12 UTC

[jira] [Commented] (ATLAS-759) HiveHookIT.testAlterTableChangeColumn is consistently failing on master

    [ https://issues.apache.org/jira/browse/ATLAS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275293#comment-15275293 ] 

Hemanth Yamijala commented on ATLAS-759:
----------------------------------------

We seem to be running into ATLAS-503. The exception is similar to the one in the log trace attached on that bug, and the situation is the same as well - in that, the message from the HiveHookIT is causing threads to issue an update, while at the same time the test is making read calls to check if the update has passed or not.

> HiveHookIT.testAlterTableChangeColumn is consistently failing on master
> -----------------------------------------------------------------------
>
>                 Key: ATLAS-759
>                 URL: https://issues.apache.org/jira/browse/ATLAS-759
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>            Priority: Blocker
>
> Running mvn clean install is failing in HiveHookIT.testAlterTableChangeColumn. The exception is occurring due to a lock timeout exception on the server side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)