Thanks @Leonard Xu <xbjt...@gmail.com>. Two minor versions are definitely
needed for flip the configs.

On Mon, Oct 30, 2023 at 8:55 PM Leonard Xu <xbjt...@gmail.com> wrote:

> Thanks @Peter for driving this FLIP
>
> +1 from my side, the timestamp semantics mapping looks good to me.
>
> >  In the end, the legacy behavior will be dropped in
> > Flink 2.0
> > I don’t think we can drop this option which introduced in 1.19 and drop
> in 2.0, the API removal requires at least two minor versions.
>
>
> Best,
> Leonard
>
> > 2023年10月31日 上午11:18,Peter Huang <huangzhenqiu0...@gmail.com> 写道:
> >
> > Hi Devs,
> >
> > Currently, Flink Avro Format doesn't support the Avro time (milli/micros)
> > with local timezone type.
> > Although the Avro timestamp (millis/micros) type is supported and is
> mapped
> > to flink timestamp without timezone,
> > it is not compliant to semantics defined in Consistent timestamp types in
> > Hadoop SQL engines
> > <
> https://docs.google.com/document/d/1gNRww9mZJcHvUDCXklzjFEQGpefsuR_akCDfWsdE35Q/edit#heading=h.n699ftkvhjlo
> >
> > .
> >
> > I propose to support Avro timestamps with the compliance to the mapping
> > semantics [1] by using a configuration flag.
> > To keep back compatibility, current mapping is kept as default behavior.
> > Users can explicitly turn on the new mapping
> > by setting it to false. In the end, the legacy behavior will be dropped
> in
> > Flink 2.0
> >
> > Looking forward to your feedback.
> >
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-378%3A+Support+Avro+timestamp+with+local+timezone
> >
> >
> > Best Regards
> >
> > Peter Huang
>
>

Reply via email to