hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-3712) Use varbinary instead of longvarbinary to store min and max column values in column stats schema
Date Wed, 28 Nov 2012 02:44:59 GMT

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

Ashutosh Chauhan updated HIVE-3712:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.10.0
           Status: Resolved  (was: Patch Available)

Taken care of in HIVE-3678
                
> Use varbinary instead of longvarbinary to store min and max column values in column stats
schema
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3712
>                 URL: https://issues.apache.org/jira/browse/HIVE-3712
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Statistics
>    Affects Versions: 0.9.0
>            Reporter: Shreepadma Venugopalan
>            Assignee: Shreepadma Venugopalan
>             Fix For: 0.10.0
>
>
> JDBC type longvarbinary maps to BLOB SQL type in some databases. Storing min and max
column values for numeric types takes up 8 bytes and hence doesn't require a BLOB. Storing
these values in a BLOB will impact performance without providing much benefits. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message