+1. This option was original configured as ‘false’ because I want to avoid this bad behavior of orc format in new version.
Considering the significant compatibility impact and the new version is using parquet as default format, I agree the default value should be configured as ‘true’ to avoid upgrade incompatibility while minimizing the impact on new users. However, I think we still need a way to tell new users to avoid this bad behavior of orc format when using versions greater than 1.0 if the default value is setting as true. yu zelin <yuzelin....@gmail.com>于2025年4月28日 周一13:11写道： > +1. > > Best, > Zelin Yu > > On Mon, Apr 28, 2025 at 4:09 PM JUNHAO YE <yejunhao12...@gmail.com> wrote: > > > +1 > > Okay for me. > > > > > 2025年4月28日 16:02，Jingsong Li <jingsongl...@gmail.com> 写道： > > > > > > Hi everyone, > > > > > > The default behavior of 'orc.timestamp-ltz.legacy.type' has been > > > changed, this has caused a significant impact on old versions of > > > tables, as a large number of tables have become incompatible due to > > > this change. > > > > > > We should not introduce such a large incompatibility error, even if it > > > is a bad behavior, it should be maintained. > > > > > > What do you think? > > > > > > Best, > > > Jingsong > > > > >
