AngersZhuuuu opened a new pull request #26934: [SPARK-30293][SQL] Remove closeTimestamp!=0 statement since we add a close status URL: https://github.com/apache/spark/pull/26934 ### What changes were proposed in this pull request? Since we have add a close status for each statement, here we should use closeTimestamp. If not when too many statement , we may remove statement that not closed, then if client call CloseStatement, we will get an error when call `onStatementClosed()` since we don't have this statement's execution info in executionList. ### Why are the changes needed? Fix bug ### Does this PR introduce any user-facing change? NO ### How was this patch tested? Don't need UT
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
