Hi Dawid, I'll try your suggestion [2] and wait for [1] to be supported in next versions.
Thanks, p.s. It's not easy to insert the timestamp into the body because it will affect other applications. In this regard, I hope [1] is going to be available soon. Dongwon On Tue, Aug 11, 2020 at 4:31 PM Dawid Wysakowicz <dwysakow...@apache.org> wrote: > I'm afraid it is not supported yet. The discussion[1] to support it > started in the past, but unfortunately it has not concluded yet. > > One approach I can think of, how you can work this limitation around is to > provide your own Format[2]. Unfortunately it is not the most > straightforward solution. > > Best, > > Dawid > > [1] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-107%3A+Reading+table+columns+from+different+parts+of+source+records > > [2] > https://ci.apache.org/projects/flink/flink-docs-release-1.11/dev/table/sourceSinks.html#encoding--decoding-formats > On 11/08/2020 09:20, Dongwon Kim wrote: > > Hi, > > I'm working on a Kafka topic where timestamps are not shown in the message > body, instead in the message's metadata. > > I want to declare a table from the topic with DDL but > "rowtime_column_name" in the below definition seems to accept only existing > columns. > >> WATERMARK FOR rowtime_column_name AS watermark_strategy_expression. > > > Can I define watermarks in this situation where timestamps are shown only > in the metadata? > > Thanks, > > Dongwon > >
