[
https://issues.apache.org/jira/browse/BEAM-4707?focusedWorklogId=119412&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-119412
]
ASF GitHub Bot logged work on BEAM-4707:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jul/18 15:43
Start Date: 05/Jul/18 15:43
Worklog Time Spent: 10m
Work Description: echauchot edited a comment on issue #5889: [BEAM-4707]
insert timestamp to bigQuery as seconds as expected by BigQuery
URL: https://github.com/apache/beam/pull/5889#issuecomment-402758127
What you mentioned in you last comment is true, it is the exact reason on
this PR: to change timestamp to use seconds instead of milliseconds otherwise
year gets out of range.
Besides, indeed after this PR is merged we will drop all nexmark tables (old
ones before timestamp inclusion and also the ones that contain long timestamps).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 119412)
Time Spent: 4h 10m (was: 4h)
> Change fields and table names in nexmark perfkit tables
> -------------------------------------------------------
>
> Key: BEAM-4707
> URL: https://issues.apache.org/jira/browse/BEAM-4707
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Fix For: 2.6.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Nexmark BQ tables for perfkit lack timestamp field. Also the table name
> contains a boolean than shows the mode of execution. It would be better to
> have batch or streaming label in place of the boolean.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
