[
https://issues.apache.org/jira/browse/HIVE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901925#comment-14901925
]
Prasanth Jayachandran commented on HIVE-11911:
----------------------------------------------
JDBCStats publishing is having all sorts of issues with key prefix. I don't
think thats a problem with counter and fs based stats. Do we really need to
support it? [~ashutoshc] Any thoughts on this?
Excerpt from this link
http://dba.stackexchange.com/questions/76469/mysql-varchar-length-and-performance
"It has some consequences for InnoDB, too. Index size is restricted to 3072
bytes and single column indexes, to 767 bytes."
> The stats table limits are too large for innodb
> -----------------------------------------------
>
> Key: HIVE-11911
> URL: https://issues.apache.org/jira/browse/HIVE-11911
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-11911.patch
>
>
> The limits were increased to a reasonable value some time ago, apparently
> these values are too large for innodb due to some index limit nonsense. We
> need to decrease them a little bit.
> There's no need to decrease them in an upgrade script; if they were already
> created successfully it's ok to have them as is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
