[jira] [Commented] (HIVE-3665) Allow URIs without port to be specified in metatool

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on HIVE-3665:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3665: Allow URIs without port to be specified in metatool (Shreepadma via Ashutosh Chauhan) (Revision 1414512)

     Result = ABORTED
hashutosh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1414512
Files : 
* /hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/tools/HiveMetaTool.java

                
> Allow URIs without port to be specified in metatool
> ---------------------------------------------------
>
>                 Key: HIVE-3665
>                 URL: https://issues.apache.org/jira/browse/HIVE-3665
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.10.0
>            Reporter: Shreepadma Venugopalan
>            Assignee: Shreepadma Venugopalan
>             Fix For: 0.11.0
>
>         Attachments: HIVE-3665.1.patch.txt
>
>
> Metatool should accept input URIs where one URI contains a port and the other doesn't. While metatool today accepts input URIs without the port when both the input URIs (oldLoc and newLoc) don't contain the port, we should make the tool a little more flexible to allow for the case where one URI contains a valid port and the other input URI doesn't. This makes more sense when transitioning to HA and a user chooses to specify the port as part of the oldLoc, but the port doesn't mean much for the newLoc.

--
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