[
https://issues.apache.org/jira/browse/HIVE-16123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902754#comment-15902754
]
Jesus Camacho Rodriguez edited comment on HIVE-16123 at 3/9/17 9:21 AM:
------------------------------------------------------------------------
[~leftylev], no need, the max property was already in HiveConf, but it was not
used properly. The granularity is an internal parameter that is inferred
automatically. Thanks
was (Author: jcamachorodriguez):
[~leftylev], no need, the max property was already in HiveConf, but it was not
used property. The granularity is an internal parameter that is inferred
automatically. Thanks
> Let user pick the granularity of bucketing and max in row memory
> ----------------------------------------------------------------
>
> Key: HIVE-16123
> URL: https://issues.apache.org/jira/browse/HIVE-16123
> Project: Hive
> Issue Type: Bug
> Components: Druid integration
> Reporter: slim bouguerra
> Assignee: slim bouguerra
> Fix For: 2.2.0
>
> Attachments: HIVE-16123.2.patch, HIVE-16123.patch
>
>
> Currently we index the data with granularity of none which puts lot of
> pressure on the indexer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
