[
https://issues.apache.org/jira/browse/HIVE-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223239#comment-16223239
]
Alexander Behm commented on HIVE-15670:
---------------------------------------
Thanks for the response. From the perspective of a client issuing an RPC to
alter column stats, it seems like a rather questionable side-effect to also
alter the table metadata with a pretty big payload. Instead of "fixing" this
issue by changing the database schema, could we instead remove the JSON string
altogether?
I'm definitely not familiar with the implementation details, just trying to
provide a perspective from a Metastore client that is not Hive.
> column_stats_accurate may not fit in PARTITION_PARAMS.VALUE
> -----------------------------------------------------------
>
> Key: HIVE-15670
> URL: https://issues.apache.org/jira/browse/HIVE-15670
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
>
> The JSON can be too big with many columns (see setColumnStatsState method).
> We can make JSON more compact by only storing the list of columns with true
> values. Or we can even store a bitmask in a dedicated column, and adjust it
> when altering table (rare enough). Or we can just change the VALUE column to
> text blob (might be a painful change wrt upgrade scripts, and supporting all
> the DBs' varied blob implementations, esp. in directsql).
> Storing denormalized flags in a separate table will probably be slow,
> comparatively.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
