[
https://issues.apache.org/jira/browse/HIVE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660813#comment-13660813
]
Gunther Hagleitner commented on HIVE-4518:
------------------------------------------
[~appodictic], thanks for confirming, I had a sneaking suspicion that was the
case. It does make the a lot code simpler, if we don't have to maintain that.
> Counter Strike: Operation Operator
> ----------------------------------
>
> Key: HIVE-4518
> URL: https://issues.apache.org/jira/browse/HIVE-4518
> Project: Hive
> Issue Type: Bug
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Attachments: HIVE-4518.1.patch, HIVE-4518.2.patch, HIVE-4518.3.patch
>
>
> Queries of the form:
> from foo
> insert overwrite table bar partition (p) select ...
> insert overwrite table bar partition (p) select ...
> insert overwrite table bar partition (p) select ...
> Generate a huge amount of counters. The reason is that task.progress is
> turned on for dynamic partitioning queries.
> The counters not only make queries slower than necessary (up to 50%) you will
> also eventually run out. That's because we're wrapping them in enum values to
> comply with hadoop 0.17.
> The real reason we turn task.progress on is that we need CREATED_FILES and
> FATAL counters to ensure dynamic partitioning queries don't go haywire.
> The counters have counter-intuitive names like C1 through C1000 and don't
> seem really useful by themselves.
> With hadoop 20+ you don't need to wrap the counters anymore, each operator
> can simply create and increment counters. That should simplify the code a lot.
--
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
