Hello, As usual I would advise against sudden drop of functionality, especially SQL syntax. It would be better if we could disable/issue a warning in one release and drop in the next to give users at least some time to digest the changes.
How about the following: In 4.0, disable the functionality by default and throw an error when used but still give the user the means to enable it back via a property. In 4.1, everything is gone; syntax + property + whatever else we want. Best, Stamatis On Wed, Aug 2, 2023 at 3:35 PM László Bodor <bodorlaszlo0...@gmail.com> wrote: > > LOL, this title, I meant *list bucketing, *oh god, this is history now, > mail archives don't forget > > https://cwiki.apache.org/confluence/display/Hive/ListBucketing > > > László Bodor <bodorlaszlo0...@gmail.com> ezt írta (időpont: 2023. aug. 2., > Sze, 11:01): > > > Hey Hive devs! > > > > What about removing list bucketing from hive? > > https://issues.apache.org/jira/browse/HIVE-17852 > > > > I remember I tried this, but the patch became huge, so I'm thinking about > > simply disabling the syntax first for 4.0 (making the user unable to create > > a table like that), and then we can gradually remove it from the codebase. > > > > Why: see details in jira. > > > > Regards, > > Laszlo Bodor > > > >
