[jira] [Updated] (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:all-tabpanel ] ASF GitHub Bot updated HIVE-26266: -- Labels: metastore_translator pull-request-available (was: metastore_translator) > 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)
[jira] [Updated] (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:all-tabpanel ] Zoltan Haindrich updated HIVE-26266: Labels: metastore_translator (was: ) > 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 > > 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)
[jira] [Updated] (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:all-tabpanel ] Sourabh Badhya updated HIVE-26266: -- Description: 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. (was: Currently CTAS considers only default table location when mapping the location to the FileSinkOperator. This will miss the cases when a custom location specified as well as when the table has a translated location.) > 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 > > 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)
[jira] [Updated] (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:all-tabpanel ] Sourabh Badhya updated HIVE-26266: -- Description: Currently CTAS considers only default table location when mapping the location to the FileSinkOperator. This will miss the cases when a custom location specified as well as when the table has a translated location. > 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 > > Currently CTAS considers only default table location when mapping the > location to the FileSinkOperator. This will miss the cases when a custom > location specified as well as when the table has a translated location. -- This message was sent by Atlassian Jira (v8.20.7#820007)
