[
https://issues.apache.org/jira/browse/HIVE-28952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014073#comment-18014073
]
Denys Kuzmenko edited comment on HIVE-28952 at 8/15/25 9:19 AM:
----------------------------------------------------------------
[~neer393] I don't understand what have you optimized here.
You are still doing multiple calls: 1 to get table names and another to get
table objects. Why not get table objects directly?
Also, have you considered the memory impact when loading everything into the
heap? You could have iterated over TableIterable instead. I don't think that is
a robust solution, it can potentially lead to OOM.
cc [~dengzh], [~wechar] [, |https://github.com/wecharyu] [~abstractdog]
was (Author: dkuzmenko):
[~neer393] I don't understand what have you optimized here.
You are still doing multiple calls: 1 to get table names and another to get
table objects. Why not get table objects directly?
Also, have you considered the memory impact when loading everything into the
heap? You could have iterated over TableIterable instead. I don't think that is
a robust solution, it can potentially lead to OOM.
cc [~dengzh], [~wechar] [, |https://github.com/wecharyu] [~abstractdog]
> TableFetcher to return Table objects instead of names
> -----------------------------------------------------
>
> Key: HIVE-28952
> URL: https://issues.apache.org/jira/browse/HIVE-28952
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: Neeraj Khatri
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.2.0
>
>
> follow-up on HIVE-28930
> {code}
> // TODO: Future improvement – modify TableFetcher to return HMS Table
> API objects directly,
> // avoiding the need for subsequent msc.getTable calls to fetch each
> matched table individually
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
