Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently CalcitePlanner generates a complete JdbcSchema for every JdbcTable in the query.
This wastes some resources since every call to JdbcSchema#getTable needs to communicate with the database to bring back the tables belonging to the schema. Moreover, the fact that a schema is created during planning is counter-intuitive since in principle the schema shouldn't change.
Attachments
Issue Links
- is related to
-
HIVE-25530 AssertionError when query involves multiple JDBC tables and views
- Closed