hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <>
Subject [jira] [Commented] (HIVE-7618) TestDDLWithRemoteMetastoreSecondNamenode unit test failure
Date Wed, 06 Aug 2014 21:31:16 GMT


Jason Dere commented on HIVE-7618:

I think the point of the test is that the test case should work properly without explicitly
setting the table location. What I think we need here is a way to determine if the StorageHandler
needs a location or not. We can either 
1. Add a new method to the StorageHandler interface (needsLocation()?), which we use in place
of StorageDescriptor.isSetLocation(). The downside to this would be that this may break any
existing 3rd party StorageHandlers, as mentioned in HIVE-6853.
2. DDLTask already has some HBaseStorageHandler-specific logic in showCreateTable(). We could
make this logic into a needsLocation() routine within DDLTask itself, and use it in a similar
way as described in (1).

> TestDDLWithRemoteMetastoreSecondNamenode unit test failure
> ----------------------------------------------------------
>                 Key: HIVE-7618
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-7618.1.patch
> Looks like TestDDLWithRemoteMetastoreSecondNamenode started failing after HIVE-6584 was
> {noformat}
> TestDDLWithRemoteMetastoreSecondNamenode.testCreateTableWithIndexAndPartitionsNonDefaultNameNode:272->createTableAndCheck:201->createTableAndCheck:219
Table should be located in the second filesystem expected:<[hdfs]> but was:<[pfile]>
> {noformat}

This message was sent by Atlassian JIRA

View raw message