[
https://issues.apache.org/jira/browse/HIVE-15430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam updated HIVE-15430:
---------------------------------
Attachment: HIVE-15430.1.patch
Attaching a patch that contains the following fixes
1) The SchemaTool's schema table validator now parses the respective schema
file (based on the dbType specfied). Prior to this change, it always parses the
oracle schema files (because the syntax is easier). For ex: for mysql, it
parses the hive-schema-xxx.mysql.sql file.
2) The error reporting/messages were not very clear or consistent when
a) VERSION table was missing
b) VERSION table had no version infor
c) VERSION table had an unrecognized version. The tool would throw a
FileNotFOundException as it could not find the schema file corresponding to
that version.
3) Table Location validator did not validate the location column in
SKEWED_COL_VALUE_LOC_MAP table. Added a validator for that column value.
> Change SchemaTool table validator to test based on the dbType
> -------------------------------------------------------------
>
> Key: HIVE-15430
> URL: https://issues.apache.org/jira/browse/HIVE-15430
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Affects Versions: 2.2.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Minor
> Attachments: HIVE-15430.1.patch
>
>
> Currently the validator parses the "oracle" schema file to determine what
> tables are expected in the database. (mostly because of ease of parsing the
> schema file compared to other syntax). We have learnt from HIVE-15118, that
> not all schema files have the same amount of tables. For example, derby has
> an old table that is never used that other DBs do not contain).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
