Details
-
New Feature
-
Status: Resolved
-
P2
-
Resolution: Implemented
-
None
-
None
Description
Currently we use Calcite Handler for NonCumulativeCost. We need to implement our own handler before implementing our own Cost model because of the following reasons:
1- We need to empty the MetadataQuery cache every time that we need to get the new cost.
2- We need to have our own method for estimating the costs instead of computeSelfCost. This is because currently we cannot set the costFactory in JDBC path and therefore that path still uses Calcite's cost model; later if we set the costFactory correctly there, we may decide to override computeSelfCost instead.
Attachments
Issue Links
- links to