SHOW CREATE TABLE return managed table path as external_location for hive connector

[Kundannitp]

Problem Statement:
SHOW CREATE TABLE cmd for hive connector is returning managed table path as external_location causing confusion that the table is managed or external and violates the Principle of Least Surprise.

Steps to reproduce:

1. Create a schema:
   CREATE SCHEMA hive.some_hive

2. Create a managed table: ""
   CREATE TABLE hive.some_hive.new_table(id int, name varchar);

3. show create table hive.some_hive.new_table;

Current Output:
trino> show create table hive.some_hive.new_table;
Create Table
--------------------------------------------------------------------------------------------
CREATE TABLE hive.some_hive.new_table (
id integer,
name varchar
)
WITH (
external_location = 'hdfs://localhost:9000/user/hive/warehouse/some_hive.db/new_table',
format = 'ORC'
)
(1 row)

Query 20260227_172350_00005_3ugvw, FINISHED, 1 node
Splits: 1 total, 1 done (100.00%)
0.37 [0 rows, 0B] [0 rows/s, 0B/s]

trino>

Expected output:
The "external_location" keyword should be either "location" or it should not be present for managed table at all.

Trino Version:
Compiled from master

[Kundannitp]

While investigating the code, I realized why this issue slipped past the current test suite. There is a slight behavioral discrepancy between a real-world Hive Metastore and Trino's mocked test environment.

Real-world scenario (Hive 3.x+): When running against a real cluster, the Hive Metastore enforces strict ACID rules. When Trino sends a "create managed table" request, Hive intercepts it and silently converts it into an EXTERNAL_TABLE to bypass ACID requirements. Later, when Trino runs SHOW CREATE TABLE, it checks the table type, sees EXTERNAL_TABLE, and blindly appends the default managed warehouse path as the external_location.

Test environment scenario: Trino's standard unit tests (like testShowCreateTable) rely on a lightweight, file-based metastore (FileHiveMetastore). This mock environment does not enforce Hive 3.x silent conversions. It saves the table strictly as a MANAGED_TABLE. Because the table type remains MANAGED, the code correctly omits the external_location, causing the test to pass and completely masking the real-world bug.