You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sourabh Badhya (Jira)" <ji...@apache.org> on 2022/05/31 06:28:00 UTC

[jira] [Commented] (HIVE-26266) Column information is not present in lineage for CTAS when custom location/translated location is used

    [ https://issues.apache.org/jira/browse/HIVE-26266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544152#comment-17544152 ] 

Sourabh Badhya commented on HIVE-26266:
---------------------------------------

Hi [~kgyrtkirk] ,
Please review this patch. As you can see after creating the PR, the tests fail because the q.out files are missing the column information in their lineage output. Kindly confirm if this is a valid bug.

Test run link - [http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3331/1/tests]

Thanks.

> 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: 10m
>  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)