For that case, I believe it's enough for us to revise the deprecation message only by making sure that Apache Spark will keep it without removal for backward-compatibility purposes only. That's what the users asked, isn't that?
> deprecation of Trigger.Once confuses users that the trigger won't be available sooner (though we rarely remove public API). The feature was deprecated in Apache Spark 3.4.0 and `Undeprecation(?)` may cause another confusion in the community, not only for Trigger.Once but also for all historic `Deprecated` items. Dongjoon. On Fri, Apr 19, 2024 at 7:44 PM Jungtaek Lim <kabhwan.opensou...@gmail.com> wrote: > Hi dev, > > I'd like to raise a discussion to un-deprecate Trigger.Once in future > releases. > > I've proposed deprecation of Trigger.Once because it's semantically broken > and we made a change, but we've realized that there are really users who > strictly require the behavior of Trigger.Once (only run a single batch in > whatever reason) despite the semantic issue, and workaround with > Trigger.AvailableNow is arguably much more hacky or sometimes not even > possible. > > I still think we have to advise using Trigger.AvailableNow whenever > feasible, but deprecation of Trigger.Once confuses users that the trigger > won't be available sooner (though we rarely remove public API). So maybe > warning log on usage sounds to me as a reasonable alternative. > > Thoughts? > > Thanks, > Jungtaek Lim (HeartSaVioR) >
