In current code of EnumerableTableScan, methods of equals and hashCode are overridden for matching of {{EnumerableTableScan}}s.
While after optimizing with the same HEP planner, {{EnumerableTableScan}}s from two plans but with the same digest will the share the same Java object. See RelOptMaterializations.
I think it's ok to remove the redundant overriding methods in EnumerableTableScan.
- is related to
-
CALCITE-3447 Fix equivalents in method SubstitutionVisitor#go
-
- Closed
-
-
CALCITE-1216 Add new rules for Materialised view optimisation of join queries
-
- Closed
-
- links to