Re: [DISCUSS] Un-deprecate Trigger.Once

While I understand your concern about confusion for reverting the decision on deprecation, we had a revert of deprecation against API which was deprecated for multiple years before reverting the decision. See SPARK-32686 . Maybe we had more cases,

Re: [DISCUSS] Un-deprecate Trigger.Once

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