[
https://issues.apache.org/jira/browse/BEAM-7823?focusedWorklogId=282953&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-282953
]
ASF GitHub Bot logged work on BEAM-7823:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/19 22:10
Start Date: 25/Jul/19 22:10
Worklog Time Spent: 10m
Work Description: riazela commented on issue #9159: [BEAM-7823]
Implementing a Custom NonCumulativeCost Handler
URL: https://github.com/apache/beam/pull/9159#issuecomment-515233495
I forgot to rebase before pushing, I will push again.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 282953)
Time Spent: 40m (was: 0.5h)
> 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
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
