[
https://issues.apache.org/jira/browse/HIVE-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003444#comment-17003444
]
ouchengeng commented on HIVE-22669:
-----------------------------------
The two patches are the same. I just submitted a patch to make it in PATCH
AVAILABLE status.
> Do not initiate Deserializer for DescTable operation when it's not needed
> -------------------------------------------------------------------------
>
> Key: HIVE-22669
> URL: https://issues.apache.org/jira/browse/HIVE-22669
> Project: Hive
> Issue Type: Improvement
> Components: Clients, Hive
> Affects Versions: 3.0.0, 4.0.0
> Reporter: ouchengeng
> Assignee: ouchengeng
> Priority: Major
> Attachments: HIVE-22669.patch, HIVE-22669.patch
>
>
> For `desc table ` queries, DescTableOperation always creates a Deserializer
> object, even though it's not often needed.
> What is worse is that if a table is backed on some particular SerDe class,
> uses have no chance to desc table without adding appropriate jar files. With
> this patch, users at least are able to desc tables when they only need
> metadata of the table, especially in a shared Hive environment.
> For above two reasons, it's better to create Deserializer object only when
> it's needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
