[
https://issues.apache.org/jira/browse/HIVE-25336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381472#comment-17381472
]
Ayush Saxena commented on HIVE-25336:
-------------------------------------
[~anishek] I haven't introduced any new API, Have used the existing
{{getAllTableObjects}} call, it is used in other couple of cases as well, One
being {{show tables extended}} as well.
Checked with Rajesh on this, guess around ~10K tables, we won't have any any
problem as such.
In the long run if the numbers start going too high, we might try & introduce
some iterator based API or may be optimise {{getAllTableObjects}} itself in a
way how {{getListing}} works for {{FileSystems}}?, and can replace everywhere.
I can keep a task open for that
> Use single call to get tables in DropDatabaseAnalyzer
> -----------------------------------------------------
>
> Key: HIVE-25336
> URL: https://issues.apache.org/jira/browse/HIVE-25336
> Project: Hive
> Issue Type: Improvement
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Optimise
> org.apache.hadoop.hive.ql.ddl.database.drop.DropDatabaseAnalyzer.analyzeInternal(DropDatabaseAnalyzer.java:61),
> where it fetches entire tables one by one. Move to a single call. This could
> save around 20+ seconds when large number of tables are present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
