[
https://issues.apache.org/jira/browse/BEAM-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122391#comment-17122391
]
Beam JIRA Bot commented on BEAM-9209:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
>
> 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)
