[
https://issues.apache.org/jira/browse/HIVE-25615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767458#comment-17767458
]
ZhengBowen commented on HIVE-25615:
-----------------------------------
I also encountered this problem, this is indeed a very poor design
> Hive on tez will generate at least one MapContainer per 0 length file
> ---------------------------------------------------------------------
>
> Key: HIVE-25615
> URL: https://issues.apache.org/jira/browse/HIVE-25615
> Project: Hive
> Issue Type: Bug
> Components: Query Planning, Query Processor, Tez
> Affects Versions: 3.1.2
> Environment: hive-3.1.2
> tez-0.10.1
> Reporter: JackYan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When tez read a table with many partitions and those partitions contain 0
> length file only, ColumnarSplitSizeEstimator will return Integer.MAX_VALUE
> bytes length for every 0 length file.Then,TezSplitGrouper will treat those
> files as big files,and generate at least one MapContainer per 0 file to
> handle it.This is incorrect and even wasteful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
