csurong opened a new issue, #4368:
URL: https://github.com/apache/amoro/issues/4368

   ### What happened?
   
   A plain Hive table can be opened successfully in the dashboard. Clicking 
Tables in the sidebar afterwards opens the generic table details page with the 
same catalog, database and table name. The request fails with "Table ... does 
not exist", even though the Hive table exists and its schema was just displayed.
   
   Expected: clicking Tables returns to the table browser, where another table 
can be selected.
   
   ### Affects Versions
   
   0.9-SNAPSHOT (15cb08da6)
   
   ### What table formats are you seeing the problem on?
   
   _No response_
   
   ### What engines are you seeing the problem on?
   
   _No response_
   
   ### How to reproduce
   
   1. Configure a Hive metastore catalog containing a plain Hive table.
   2. Open Tables, expand the catalog and database, and select the Hive table.
   3. Confirm that its schema is displayed on /hive-tables.
   4. Click Tables in the sidebar.
   5. The dashboard navigates to /tables with the cached table identifier and 
requests /details instead of /hive/details. The response reports that the table 
does not exist.
   
   ### Relevant log output
   
   ```shell
   org.apache.amoro.NoSuchTableException: Table: <table_name> does not exist.
       at 
org.apache.amoro.CommonUnifiedCatalog.loadTable(CommonUnifiedCatalog.java:135)
   ```
   
   ### Anything else
   
   Sidebar.vue restores the cached table identifier but always routes to 
/tables. The table browser already saves expanded catalog and database nodes 
separately in sessionStorage, so returning to the browser does not require 
reopening the cached table.
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's Code of Conduct


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to