hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ouchengeng (Jira)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-22669) Do not initiate Deserializer for DescTable operation when it's not needed
Date Tue, 24 Dec 2019 09:19:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ouchengeng updated HIVE-22669:
------------------------------
    Attachment: HIVE-22669.patch

> 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
>            Reporter: ouchengeng
>            Assignee: ouchengeng
>            Priority: Major
>         Attachments: 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 an open 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)

Mime
View raw message