Possibility Split Parquet file

Hi @HadoopHero ,

For Hive, if there is a single reduce task to write the output data it will not break it up the output file into smaller files, that's expected and cannot be configured to behave in a different way.

With DISTRIBUTE BY you should be able to achieve to have multiple reducers (if you have a column by which you can "split" your data reasonably into smaller subsets), see

https://cwiki.apache.org/confluence/display/Hive/LanguageManual+SortBy

Best regards

 Miklos

Hello Miklos,

unfortunately, what you suggested had no effect. We continue to have the same problem, with creating a single parquet file.

Hi @HadoopHero ,

If the query involves dynamic partitioning, one potential issue is that 'hive.optimize.sort.dynamic.partition.threshold' may limit the number of open record writers to just one per partition value, resulting in the creation of only one file. To investigate this, could you attempt disabling 'hive.optimize.sort.dynamic.partition.threshold' entirely?

SET hive.optimize.sort.dynamic.partition.threshold=-1;

Note : The problem statement contains a typo in the config name

@HadoopHero Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks.

@DianaTorres I'm sorry but unfortunately the problem still persists even after trying the suggestions in the previous posts

@Shmoo @cravani Do you have any insights here? Thanks!

@HadoopHero Answer would vary based on query that you are running, assuming you have simple "Insert select */cols from Table" it is likely mapper only job and you may want to try tuning below.

set tez.grouping.min-size=134217728; -- 128 MB min split
set tez.grouping.max-size=1073741824; -- 1 GB max split

Try setting min-size and max-size to same value. I would not go below 128M.

@HadoopHero Has the reply helped resolve your issue? Thanks.