You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2024/04/09 14:54:00 UTC

[jira] [Resolved] (HIVE-6190) redundant columns in metastore schema for stats

     [ https://issues.apache.org/jira/browse/HIVE-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denys Kuzmenko resolved HIVE-6190.
----------------------------------
    Fix Version/s: 4.1.0
       Resolution: Duplicate

> redundant columns in metastore schema for stats
> -----------------------------------------------
>
>                 Key: HIVE-6190
>                 URL: https://issues.apache.org/jira/browse/HIVE-6190
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Minor
>             Fix For: 4.1.0
>
>
> package.jdo has:
> {noformat}
>       <field name ="dbName">
>         <column name="DB_NAME" length="128" jdbc-type="VARCHAR" allows-null="false"/>
>       </field>
>       <field name="tableName">
>         <column name="TABLE_NAME" length="128" jdbc-type="VARCHAR" allows-null="false"/>
>       </field>
>       <field name="partitionName">
>         <column name="PARTITION_NAME" length="767" jdbc-type="VARCHAR" allows-null="false"/>
>       </field>
>       <field name="partition">
>         <column name="PART_ID"/>
>       </field>
> {noformat}
> Only PART_ID is enough, the other fields are unnecessary and may potentially cause bugs; similarly for table stats. One could argue that they were intended for perf (denormalization), but stats retrieval currently is very slow on much deeper level so it's not really justified.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)