[ https://issues.apache.org/jira/browse/HIVE-27168?focusedWorklogId=852848&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-852848 ]
ASF GitHub Bot logged work on HIVE-27168: ----------------------------------------- Author: ASF GitHub Bot Created on: 24/Mar/23 12:56 Start Date: 24/Mar/23 12:56 Worklog Time Spent: 10m Work Description: SourabhBadhya commented on code in PR #4144: URL: https://github.com/apache/hive/pull/4144#discussion_r1147527514 ########## standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java: ########## @@ -1327,7 +1327,7 @@ public void visit(LeafNode node) throws MetaException { return; } - String colTypeStr = partitionKeys.get(partColIndex).getType(); + String colTypeStr = MetaStoreUtils.getBaseNameOfColType(partitionKeys.get(partColIndex).getType()); Review Comment: Yes you are right. Changed it. Done. Issue Time Tracking ------------------- Worklog Id: (was: 852848) Time Spent: 2h 40m (was: 2.5h) > Use basename of the datatype when fetching partition metadata using partition > filters > ------------------------------------------------------------------------------------- > > Key: HIVE-27168 > URL: https://issues.apache.org/jira/browse/HIVE-27168 > Project: Hive > Issue Type: Bug > Reporter: Sourabh Badhya > Assignee: Sourabh Badhya > Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > While fetching partition metadata using partition filters, we use the column > type of the table directly. However, char/varchar types can contain extra > information such as length of the char/varchar column and hence it skips > fetching partition metadata due to this extra information. > Solution: Use the basename of the column type while deciding on whether > partition pruning can be done on the partitioned column. -- This message was sent by Atlassian Jira (v8.20.10#820010)