From a294e74f2f688c34d2e36f8ea7732066e99d3da4 Mon Sep 17 00:00:00 2001 From: Ruifeng Zheng Date: Thu, 18 Apr 2024 18:05:53 +0800 Subject: [PATCH] update --- python/pyspark/sql/session.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/python/pyspark/sql/session.py b/python/pyspark/sql/session.py index 1098c41a3f4c8..e0c2c815c827c 100644 --- a/python/pyspark/sql/session.py +++ b/python/pyspark/sql/session.py @@ -1633,7 +1633,7 @@ def sql( Notes ----- In Spark Classic, a temporary view referenced in `spark.sql` is resolved immediately, - while in Spark Connect it is lazily evaluated. + while in Spark Connect it is lazily analyzed. So in Spark Connect if a view is dropped, modified or replaced after `spark.sql`, the execution may fail or generate different results. @@ -1766,7 +1766,7 @@ def table(self, tableName: str) -> DataFrame: Notes ----- In Spark Classic, a temporary view referenced in `spark.table` is resolved immediately, - while in Spark Connect it is lazily evaluated. + while in Spark Connect it is lazily analyzed. So in Spark Connect if a view is dropped, modified or replaced after `spark.table`, the execution may fail or generate different results.