[ 
https://issues.apache.org/jira/browse/HIVE-24545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-24545:
--------------------------------
    Description: 
I found this while IOW on TPCDS 10TB:

{code}
----------------------------------------------------------------------------------------------
        VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING  PENDING  
FAILED  KILLED
----------------------------------------------------------------------------------------------
Map 1 ..........      llap     SUCCEEDED   4210       4210        0        0    
   0     362
Reducer 2 ......      llap     SUCCEEDED    101        101        0        0    
   0       2
Reducer 3 ......      llap     SUCCEEDED   1009       1009        0        0    
   0       1
----------------------------------------------------------------------------------------------
VERTICES: 03/03  [==========================>>] 100%  ELAPSED TIME: 12613.62 s
----------------------------------------------------------------------------------------------
20/12/16 01:37:36 [main]: WARN jdbc.HiveStatement: Number of rows is greater 
than Integer.MAX_VALUE
{code}

my scenario was:
{code}
set hive.exec.max.dynamic.partitions=2000;
drop table if exists test_sales_2;
create table test_sales_2 like tpcds_bin_partitioned_acid_orc_10000.store_sales;
insert overwrite table test_sales_2 select * from 
tpcds_bin_partitioned_acid_orc_10000.store_sales where ss_sold_date_sk > 
2451868;
{code}

regaridng affected row numbers:
{code}
select count(*) from tpcds_bin_partitioned_acid_orc_10000.store_sales where 
ss_sold_date_sk > 2451868;
+--------------+
|     _c0      |
+--------------+
| 12287871907  |
+--------------+
{code}

I guess we should switch to long

> jdbc.HiveStatement: Number of rows is greater than Integer.MAX_VALUE
> --------------------------------------------------------------------
>
>                 Key: HIVE-24545
>                 URL: https://issues.apache.org/jira/browse/HIVE-24545
>             Project: Hive
>          Issue Type: Bug
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Minor
>
> I found this while IOW on TPCDS 10TB:
> {code}
> ----------------------------------------------------------------------------------------------
>         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING  PENDING  
> FAILED  KILLED
> ----------------------------------------------------------------------------------------------
> Map 1 ..........      llap     SUCCEEDED   4210       4210        0        0  
>      0     362
> Reducer 2 ......      llap     SUCCEEDED    101        101        0        0  
>      0       2
> Reducer 3 ......      llap     SUCCEEDED   1009       1009        0        0  
>      0       1
> ----------------------------------------------------------------------------------------------
> VERTICES: 03/03  [==========================>>] 100%  ELAPSED TIME: 12613.62 s
> ----------------------------------------------------------------------------------------------
> 20/12/16 01:37:36 [main]: WARN jdbc.HiveStatement: Number of rows is greater 
> than Integer.MAX_VALUE
> {code}
> my scenario was:
> {code}
> set hive.exec.max.dynamic.partitions=2000;
> drop table if exists test_sales_2;
> create table test_sales_2 like 
> tpcds_bin_partitioned_acid_orc_10000.store_sales;
> insert overwrite table test_sales_2 select * from 
> tpcds_bin_partitioned_acid_orc_10000.store_sales where ss_sold_date_sk > 
> 2451868;
> {code}
> regaridng affected row numbers:
> {code}
> select count(*) from tpcds_bin_partitioned_acid_orc_10000.store_sales where 
> ss_sold_date_sk > 2451868;
> +--------------+
> |     _c0      |
> +--------------+
> | 12287871907  |
> +--------------+
> {code}
> I guess we should switch to long



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to