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

Aihua Xu commented on HIVE-16057:
---------------------------------

SchemaTool provides a way to override the user and password from the command 
line, in clear text, e.g., with different user rather than the one configured 
in the conf. 

The jira is to fix this issue that the password is not taken even if it's 
supplied through command line. 

[~pvary] Is that correct?

> SchemaTool ignores --passWord argument if 
> hadoop.security.credential.provider.path is configured
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16057
>                 URL: https://issues.apache.org/jira/browse/HIVE-16057
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>         Attachments: HIVE-16057.patch
>
>
> It the {{hadoop.security.credential.provider.path}} is defined in command 
> line, but the correct {{HADOOP_CREDSTORE_PASSWORD}} is not provided the 
> SchemaTool fails, even if the correct metastore password is provided with 
> {{--passWord}}
> Could be reproduced if the hive-site.xml contains the following:
> {code}
>   <property>
>     <name>hadoop.security.credential.provider.path</name>
>     
> <value>localjceks://file//Users/petervary/tmp/conf/creds.localjceks</value>
>   </property>
> {code}
> {code}
> $ ../schemaTool --dbType=mysql --info --passWord=pwd
> Metastore connection URL:      
> jdbc:mysql://localhost:3306/hive?useUnicode=true&characterEncoding=UTF-8
> Metastore Connection Driver :  com.mysql.jdbc.Driver
> Metastore connection User:     hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema 
> version.
> *** schemaTool failed ***
> {code}
> The {{--passWord}} argument should override the errors from the credential 
> provider



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to