You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sho Shimauchi (JIRA)" <ji...@apache.org> on 2013/01/25 06:43:12 UTC
[jira] [Commented] (HIVE-3620) Drop table using hive CLI throws
error when the total number of partition in the table is around 50K.
[ https://issues.apache.org/jira/browse/HIVE-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562444#comment-13562444 ]
Sho Shimauchi commented on HIVE-3620:
-------------------------------------
Hi Arup,
Current version of Hive fetches only 1000 partitions information at a time.
Increasing hive.metastore.batch.retrieve.table.partition.max may solve this issue.
This change can cause OOME on your client.
If you hit heap error, please increase the heap size of the client and try again.
See HIVE-2907 for more details.
> Drop table using hive CLI throws error when the total number of partition in the table is around 50K.
> -----------------------------------------------------------------------------------------------------
>
> Key: HIVE-3620
> URL: https://issues.apache.org/jira/browse/HIVE-3620
> Project: Hive
> Issue Type: Bug
> Reporter: Arup Malakar
>
> hive> drop table load_test_table_20000_0;
> FAILED: Error in metadata: org.apache.thrift.transport.TTransportException: java.net.SocketTimeoutException: Read timedout
> FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask
> The DB used is Oracle and hive had only one table:
> select COUNT(*) from PARTITIONS;
> 54839
> I can try and play around with the parameter hive.metastore.client.socket.timeout if that is what is being used. But it is 200 seconds as of now, and 200 seconds for a drop table calls seems high already.
> Thanks,
> Arup
--
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