[
https://issues.apache.org/jira/browse/HIVE-26266?focusedWorklogId=776125&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-776125
]
ASF GitHub Bot logged work on HIVE-26266:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 31/May/22 08:22
Start Date: 31/May/22 08:22
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on code in PR #3331:
URL: https://github.com/apache/hive/pull/3331#discussion_r885344481
##########
ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java:
##########
@@ -8232,6 +8232,14 @@ private void handleLineage(LoadTableDesc ltd, Operator
output)
Warehouse wh = new Warehouse(conf);
tlocation =
wh.getDefaultTablePath(db.getDatabase(tableDesc.getDatabaseName()),
tName, tableDesc.isExternal());
+
+ if (destinationTable != null) {
+ Table tbl = db.getTranslateTableDryrun(destinationTable.getTTable());
Review Comment:
isn't it a bit too late to run this? why don't we run this right away when
we are creating the `destinationTable` object?
so that we don't make the same mistake again-and-again?
Issue Time Tracking
-------------------
Worklog Id: (was: 776125)
Time Spent: 20m (was: 10m)
> Column information is not present in lineage for CTAS when custom
> location/translated location is used
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-26266
> URL: https://issues.apache.org/jira/browse/HIVE-26266
> Project: Hive
> Issue Type: Bug
> Reporter: Sourabh Badhya
> Assignee: Sourabh Badhya
> Priority: Major
> Labels: metastore_translator, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently CTAS considers only default table location when mapping the
> location to the FileSinkOperator. This will miss the cases when a custom
> location is specified as well as when the table has a translated location.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
