[ https://issues.apache.org/jira/browse/HIVE-24399?focusedWorklogId=512882&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-512882 ]
ASF GitHub Bot logged work on HIVE-24399: ----------------------------------------- Author: ASF GitHub Bot Created on: 17/Nov/20 13:00 Start Date: 17/Nov/20 13:00 Worklog Time Spent: 10m Work Description: pvary opened a new pull request #1682: URL: https://github.com/apache/hive/pull/1682 ### What changes were proposed in this pull request? - `Table.checkValidity` should use `getDeserializer` instead of `getDeserializerFromMetaStore`. This will use the cached version of the Deserializer so it will prevent creating a new one. - `SemanticAnalyzer.genConversionSelectOperator` should get a `Deserializer` as an input parameter, since we already has that at hand - When we are generating the FileSinkPlan on an destination table, we should reuse the table deserializer to get the columns whenever it is possible ### Why are the changes needed? To speed up query planning ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Unit tests ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 512882) Remaining Estimate: 0h Time Spent: 10m > Optimize Deserializer creation > ------------------------------ > > Key: HIVE-24399 > URL: https://issues.apache.org/jira/browse/HIVE-24399 > Project: Hive > Issue Type: Improvement > Reporter: Peter Vary > Assignee: Peter Vary > Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When running a query on a table using a non-default SerDe we often recreate > the Deserializer object. This could be costly and often not necessary. > We should optimize this as much as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)