kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pablo Vazquez <pablo.vazq...@globant.com>
Subject Error when creating partitions with BIGINT
Date Fri, 23 Dec 2016 22:05:33 GMT
Hi Kudu fellowship!

Happy holidays for all you guys.

Recently I tried to create a simple 4-column table using a BIGINT as part
of the PK and use the same column for partitioning by RANGE.

This is the script:

*`channel_id` BIGINT,*
*`timestamp` BIGINT,*
*`channel_name` STRING,*
*`cookie_hash` STRING*
*DISTRIBUTE BY RANGE (`timestamp`)*
*  'storage_handler' = 'com.cloudera.kudu.hive.KuduStorageHandler',*
*  'kudu.table_name' = 'kd_clicks',*
*  'kudu.master_addresses' = 'XXXXXX',*
*  'kudu.key_columns' = 'channel_id, timestamp'*

However, in the Kudu UI the partitions are not created properly:

Partition schema & range bounds

Range component:
  (timestamp int64)
Range bounds:
  [<start>, (int64 timestamp=-1213317120))
  [(int64 timestamp=-1213317120), (int64 timestamp=-151484416))
  [(int64 timestamp=-151484416), (int64 timestamp=1465082880))
  [(int64 timestamp=1465082880), <end>)

We made some tests and we found the issue appears when the partition is
defined above 2,147,483,647 (upper limit for Int-32). It seems the range
partition only accept INT32 boundaries although the column is INT64.

I'd appreciate your comments. We're not sure if we are missing something
during table creation.

*Pablo Quetzalcóatl Vázquez*| Software Designer

[image: Facebook]


The information contained in this e-mail may be confidential. It has been 
sent for the sole use of the intended recipient(s). If the reader of this 
message is not an intended recipient, you are hereby notified that any 
unauthorized review, use, disclosure, dissemination, distribution or 
copying of this communication, or any of its contents, 
is strictly prohibited. If you have received it by mistake please let us 
know by e-mail immediately and delete it from your system. Many thanks.


La información contenida en este mensaje puede ser confidencial. Ha sido 
enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de 
este mensaje no fuera el destinatario previsto, por el presente queda Ud. 
notificado que cualquier lectura, uso, publicación, diseminación, 
distribución o copiado de esta comunicación o su contenido está 
estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje 
por error le agradeceremos notificarnos por e-mail inmediatamente y 
eliminarlo de su sistema. Muchas gracias.

View raw message