[ 
https://issues.apache.org/jira/browse/BEAM-7777?focusedWorklogId=296781&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-296781
 ]

ASF GitHub Bot logged work on BEAM-7777:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Aug/19 13:56
            Start Date: 17/Aug/19 13:56
    Worklog Time Spent: 10m 
      Work Description: alexvanboxel commented on pull request #9368: 
[BEAM-7777] Fix BigQuery timestamp handling for Schema Aware PCollection
URL: https://github.com/apache/beam/pull/9368
 
 
   This fixes the handling of timestamps when reading for BigQuery. As it
   was assumed BigQuery always outputs a Double, reading a table directly
   outputs a textual version in the JSON. This is now handled. Also the
   from Beam Row also outputs the BigQuery textual version, iso the ISO
   standard representation, this makes the implementation symmetric.
   
   _Tested on DirectRunner and DataflowRunner_
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 296781)
    Time Spent: 1h 20m  (was: 1h 10m)

> Stream Cost Model and RelNode Cost Estimation
> ---------------------------------------------
>
>                 Key: BEAM-7777
>                 URL: https://issues.apache.org/jira/browse/BEAM-7777
>             Project: Beam
>          Issue Type: New Feature
>          Components: dsl-sql
>            Reporter: Alireza Samadianzakaria
>            Assignee: Alireza Samadianzakaria
>            Priority: Major
>             Fix For: Not applicable
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently the cost model is not suitable for streaming jobs. (it uses row 
> count and for estimating the output row count of each node it is using 
> calcite estimations that are only applicable to bounded data.)
> We need to implement a new cost model and implement cost estimation for all 
> of our physical nodes. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to