[
https://issues.apache.org/jira/browse/HIVE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501392#comment-13501392
]
Ashutosh Chauhan commented on HIVE-3678:
----------------------------------------
Shreepadma,
Any thoughts on how we are going to store low and high values for BigDecimal
column? Seems like there are four possibilites:
* We can add two more column in M*ColumnStatistics table of type BigDecimal:
BigDecimalLowValue and BigDecimalHighValue. But is BigDecimal type supported
consistently across different DBs?
* We can have these two columns of type Double, but then we loose precision.
* We can store as plain strings in column of type varchar.
* We can store in json format in column of type varchar.
What do you think will be the best way?
I imagine there are other numeric types too for which neither of long or double
will be a good choice. This question will come up again if we choose to add
support for these later.
> Add metastore upgrade scripts for column stats schema changes
> -------------------------------------------------------------
>
> Key: HIVE-3678
> URL: https://issues.apache.org/jira/browse/HIVE-3678
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Shreepadma Venugopalan
> Assignee: Shreepadma Venugopalan
> Fix For: 0.10.0
>
> Attachments: HIVE-3678.1.patch.txt, HIVE-3678.2.patch.txt
>
>
> Add upgrade script for column statistics schema changes for
> Postgres/MySQL/Oracle/Derby
--
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
