alamb commented on issue #14123: URL: https://github.com/apache/datafusion/issues/14123#issuecomment-2691106681
> If Expr::Wildcard no longer works, why is it still being kept around? I don't know -- maybe we should mark it deprecated > There is a concerning pattern of various zombie operations that no longer work, are surfaced in pre-release testing, and yet are still exposed to downstream users. I agree this is not good and i would like to improve the situation. > If these operations no longer serve a purpose, why don't we either remove them entirely as proper breaking changes or modify them to throw an error upon construction? One thing we have been trying to do recently is avoid just straight up breaking APIs and instead try to deprecate them (as [described here](https://datafusion.apache.org/library-user-guide/api-health.html#deprecation-guidelines)). The idea is to give downstream users some hints about what they need to change. The `ScalarUDFImpl::invoke()` saga is most unfortuntate as the deprecation warnings don't seem to get shown. > Otherwise, we are knowingly releasing bugs and breaks, which defeats the whole purpose of pre-release testing. I think this sounds like a good idea to me. I don't think we are actively trying to cause pain for downstream users, more like we struggle to find the time to properly think through all potential downstream implications -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
