Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Implemented
-
None
-
None
-
None
Description
Oracle has "RELY NOVALIDATE" option for constraints.. Could be easier for Hive to start with something like that for PK/FK constraints. So CBO has more information for optimizations. It does not have to actually check if that constraint is relationship is true; it can just "rely" on that constraint..
So it would be helpful with join cardinality estimates, and with cases like this - https://issues.apache.org/jira/browse/HIVE-13019
Attachments
Attachments
Issue Links
- Dependent
-
SPARK-17076 Cardinality estimation of join operator
-
- Resolved
-
- is related to
-
HIVE-6905 Implement Auto increment, primary-foreign Key, not null constraints and default value in Hive Table columns
-
- Open
-
-
SPARK-15302 Implement FK/PK "rely novalidate" constraints for better CBO
-
- Resolved
-
-
HIVE-16575 Support for 'UNIQUE' and 'NOT NULL' constraints
-
- Closed
-
-
HIVE-13019 Optimizer COLLECT_LIST/COLLECT_SET
-
- Open
-
-
HIVE-15342 Add support for primary/foreign keys in HBase metastore
-
- Resolved
-
- links to