You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Alireza Samadianzakaria (JIRA)" <ji...@apache.org> on 2019/07/25 21:24:00 UTC
[jira] [Updated] (BEAM-7823) Implementing Custom MetadataHandler
for NonCumulativeCost
[ https://issues.apache.org/jira/browse/BEAM-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alireza Samadianzakaria updated BEAM-7823:
------------------------------------------
Status: Open (was: Triage Needed)
> Implementing Custom MetadataHandler for NonCumulativeCost
> ---------------------------------------------------------
>
> Key: BEAM-7823
> URL: https://issues.apache.org/jira/browse/BEAM-7823
> Project: Beam
> Issue Type: New Feature
> Components: dsl-sql
> Reporter: Alireza Samadianzakaria
> Assignee: Alireza Samadianzakaria
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)