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

Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:29:43 UTC

[jira] [Commented] (HIVE-3486) CTAS in database with location on non-default name node fails

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

Hudson commented on HIVE-3486:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3486 CTAS in database with location on non-default name node fails
(Kevin Wilfong via namit) (Revision 1387850)

     Result = ABORTED
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1387850
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
* /hive/trunk/ql/src/test/queries/clientpositive/ctas_uses_database_location.q
* /hive/trunk/ql/src/test/results/clientpositive/ctas_uses_database_location.q.out

                
> CTAS in database with location on non-default name node fails
> -------------------------------------------------------------
>
>                 Key: HIVE-3486
>                 URL: https://issues.apache.org/jira/browse/HIVE-3486
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3486.1.patch.txt, HIVE-3486.2.patch.txt
>
>
> If a database has a location which is on a different name node than the default database's location, CTAS queries run in that database will fail.
> This is because the intermediate location which is where the final FileSinkOperator writes to is determined based on the scheme and authority of the value of hive.metastore.warehouse.dir instead of the table's database's location.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira