szehon-ho opened a new pull request, #50028: URL: https://github.com/apache/spark/pull/50028
### What changes were proposed in this pull request? Minor follow up for https://github.com/apache/spark/pull/49963 to use lazy vals ### Why are the changes needed? The original pr would have a small potential behavior change, if there are multiple current_ functions in the query, it could evaluate different results if the catalog is updated in the backend. Making a lazy val allows the FinishAnalysis phase to resolve one value for each current_function even in this case. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Existing unit test ### Was this patch authored or co-authored using generative AI tooling? No -- 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: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
