You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2020/01/28 19:26:00 UTC

[jira] [Comment Edited] (BEAM-9209) Add support for mapping columns to pubsub message event_timestamp when using flat schemas DDL

    [ https://issues.apache.org/jira/browse/BEAM-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025385#comment-17025385 ] 

Brian Hulette edited comment on BEAM-9209 at 1/28/20 7:25 PM:
--------------------------------------------------------------

CC: [~kenn]
I think maybe we actually need two different options here:
- one to indicate that a field should be used as the event time for watermark purposes, and
- one to map a field to publish time (making it a read-only field).

We currently do both implicitly with "event_timestamp". Is that understanding correct?


was (Author: bhulette):
CC: [~kenn]
I think maybe we actually need two different options here:
- One to indicate that a field should be used as the event time for watermark purposes, 
- and one to map a field to publish time (making it a read-only field).

We currently do both implicitly with "event_timestamp". Is that understanding correct?

> Add support for mapping columns to pubsub message event_timestamp when using flat schemas DDL
> ---------------------------------------------------------------------------------------------
>
>                 Key: BEAM-9209
>                 URL: https://issues.apache.org/jira/browse/BEAM-9209
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: Major
>
> Context: https://lists.apache.org/thread.html/bf4c37f21bda194d7f8c40f6e7b9a776262415755cc1658412af3c76%40%3Cdev.beam.apache.org%3E
> The syntax should look something like this (proposed by [~alexvanboxel]):
> {code}
> CREATE TABLE people (
>     my_timestamp TIMESTAMP *OPTION(ref="pubsub:event_timestamp)*,
>     my_id VARCHAR *OPTION(ref="pubsub:attributes['id_name']")*,
>     name VARCHAR,
>     age INTEGER
>   )
>   TYPE 'pubsub'
>   LOCATION 'projects/my-project/topics/my-topic'
> {code}
> This jira pertains specifically to the my_timestamp portion of this example.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)