[
https://issues.apache.org/jira/browse/HIVE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598597#comment-13598597
]
Alexander Alten-Lorenz commented on HIVE-4147:
----------------------------------------------
HiveMetatstoreClient is using hive.metastore.uris=thrift://<IP>:9083 to connect
to metastore service which is started as standonle mode using port 9083. We've
used HiveServer2, yes.
> Slow Hive JDBC in concurrency mode to create/drop table
> -------------------------------------------------------
>
> Key: HIVE-4147
> URL: https://issues.apache.org/jira/browse/HIVE-4147
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 0.10.0
> Reporter: Alexander Alten-Lorenz
>
> It's very slow using hive jdbc in concurrency mode to create/drop table,
> which is 20 times slower than using HiveMetatstoreClient.
> test steps:
> 1. create 100 different hive table one by one by using hive jdbc: "create
> table ......"
> 2. drop table one by one by using hive jdbc: "drop table ......" and timing
> 3. create 100 different hive table one by one by using hive jdbc: "create
> table ......"
> 4. drop tables one by one by using new
> HiveMetatstoreClient().dropTable("default", "table_name") and timing
> results
> step 2 is 20 times slower than step 4.
> basically hive jdbc is 20 times slower than HiveMetatstoreClient not only
> create/table, but also the same kind of calls.
> Dropping tables via this low level API could cause issues if there are any
> clients concurrently querying the table.
--
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
