[
https://issues.apache.org/jira/browse/HIVE-9108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-9108:
-----------------------------------
Attachment: HIVE-9108.patch
I am reverting my hashing fix.
It seems that storage layer that has the limitation is the correct place to
address the limitation, but stats code appears to have one on client layer
instead... so I am reverting to the old behavior in case if client doesn't
provide the correct key (except before it was failing with a SQL exception of
some sort, now it's explicit).
Additionally, I'm changing column size to 4000 from 255, because there's no
reason not to.
[~jdere] [~prasanth_j] can you guys take a look?
> Fix for HIVE-8735 is incorrect (stats with long paths)
> ------------------------------------------------------
>
> Key: HIVE-9108
> URL: https://issues.apache.org/jira/browse/HIVE-9108
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Fix For: 0.15.0, 0.14.1
>
> Attachments: HIVE-9108.patch
>
>
> The hashing eliminates the failure, but it seems that stats produced are
> incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
