[
https://issues.apache.org/jira/browse/HIVE-25670?focusedWorklogId=679120&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-679120
]
ASF GitHub Bot logged work on HIVE-25670:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/21 15:45
Start Date: 09/Nov/21 15:45
Worklog Time Spent: 10m
Work Description: scarlin-cloudera commented on a change in pull request
#2763:
URL: https://github.com/apache/hive/pull/2763#discussion_r745746867
##########
File path:
ql/src/java/org/apache/hadoop/hive/ql/optimizer/calcite/RelOptHiveTable.java
##########
@@ -333,12 +360,20 @@ public boolean isKey(ImmutableBitSet columns) {
parentTableQualifiedName.add(parentTableName);
qualifiedName = parentTableName;
}
+ if (!tablesCache.containsKey(qualifiedName)) {
+ // Table doesn't exist in the cache, so we don't need to track
+ // these referential constraints. But we do need to keep track
+ // of the table in case the tableCache gets populated later, though
+ // in theory, this should never happen based on how this is called.
Review comment:
I was thinking about this a little more. I'll have to review the code
to see if it's possible, but I think I can at least put in one check (that
isn't foolproof) that willl prevent a user calling for an incomplete list of
referential constraints. I can do this by ensuring that a second call
retrieving them doesn't have any missing.
Of course, if the list is incomplete and a second call isn't made, then this
won't be caught.
But I think will add this shortly.
--
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: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 679120)
Time Spent: 1h (was: 50m)
> Avoid getTable() calls for foreign key tables not used in a query
> -----------------------------------------------------------------
>
> Key: HIVE-25670
> URL: https://issues.apache.org/jira/browse/HIVE-25670
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Steve Carlin
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In RelOptHiveTable, we generate the referential constraints for the table. In
> this process, we make a metastore call to fetch these tables. This is used
> later on for potential gain on joins done on the key.
> However, there is no need to fetch these constraints if the table is not used
> in the query. If we can get this information up front, we can save a bit on
> compilation time.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
