[
https://issues.apache.org/jira/browse/HIVE-24815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289157#comment-17289157
]
Hunter Logan commented on HIVE-24815:
-------------------------------------
Making a PR for this right now. I think that for the best way to proceed is to
disable the FK constraint on 3.2, but have the table dropped completely in 4.0
> Remove "IDXS" Table from Metastore Schema
> -----------------------------------------
>
> Key: HIVE-24815
> URL: https://issues.apache.org/jira/browse/HIVE-24815
> Project: Hive
> Issue Type: Improvement
> Components: Metastore, Standalone Metastore
> Affects Versions: 3.1.0, 3.0.0, 3.1.1, 3.1.2, 3.2.0, 4.0.0
> Reporter: Hunter Logan
> Assignee: Hunter Logan
> Priority: Major
>
> In Hive 3 the rarely used "INDEXES" was removed from the DDL
> https://issues.apache.org/jira/browse/HIVE-18448
>
> There are a few issues here:
> # The Standalone-Metastore schema for Hive 3+ all include the "IDXS" table,
> which has no function.
> **
> [https://github.com/apache/hive/tree/master/standalone-metastore/metastore-server/src/main/sql/mysql]
> # The upgrade schemas from 2.x -> 3.x do not do any cleanup of the IDXS table
> ** If a user used the "INDEXES" feature in 2.x and then upgrades their
> metastore to 3.x+ they cannot drop any table that has an index on it due to
> "IDXS_FK1" constraint since the TBLS entry is referenced in the IDXS table
> ** Since INDEX is no longer in the DDL they cannot run any command from Hive
> to drop the index.
> ** Users can manually connect to the metastore and either drop the IDXS
> table or the foreign key constraint
>
> Since indexes provide no benefits in Hive 3+ it should be fine to drop them
> completely in the schema upgrade scripts. At the very least the 2.x -> 3.x+
> scripts should drop the fk constraint.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
