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

Prasad Mujumdar commented on HIVE-5449:
---------------------------------------

* Without the patch
{noformat}
$ build/dist/bin/schematool -dbType postgres -info
Metastore connection URL:        jdbc:postgresql://localhost/metastore
Metastore Connection Driver :    org.postgresql.Driver
Metastore connection User:       hive
Hive distribution version:       0.13.0
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema 
version.
*** schemaTool failed ***
{noformat}

* With the patch  
{noformat}
]$ build/dist/bin/schematool -dbType postgres -info
Metastore connection URL:        jdbc:postgresql://localhost/metastore
Metastore Connection Driver :    org.postgresql.Driver
Metastore connection User:       hive
Hive distribution version:       0.13.0
Metastore schema version:        0.13.0
schemaTool completeted
{noformat}
~                                                                               
                                        


> Hive schematool info option incorrectly reports error for Postgres metastore
> ----------------------------------------------------------------------------
>
>                 Key: HIVE-5449
>                 URL: https://issues.apache.org/jira/browse/HIVE-5449
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.12.0, 0.13.0
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
>         Attachments: HIVE-5449.1.patch
>
>
> The schema tool has an option to verify the schema version stored in the 
> metastore. This is implemented as a simple select query executed via JDBC. 
> The problem is that Postgres requires object names to be quoted due to the 
> way tables are created. It's a similar issues hit by metastore direct SQL 
> (HIVE-5264,  HIVE-5265 etc).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to