This is an automated email from the ASF dual-hosted git repository.

hello-stephen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/master by this push:
     new 532042c4dad [fix](regression) Drop view before its base tables in 
test_join5 (#65455)
532042c4dad is described below

commit 532042c4dada051fa8ea3692eaf2f4c2e14a7db3
Author: shuke <[email protected]>
AuthorDate: Thu Jul 16 18:08:08 2026 +0800

    [fix](regression) Drop view before its base tables in test_join5 (#65455)
    
    ### What problem does this PR solve?
    
    Issue Number: DORIS-23587
    
    Related PR: None
    
    Problem Summary:
    
    `test_join5` creates the `uqv1` view on top of `uq1`, but drops `uq1`
    while the view still exists. A concurrent
    `information_schema.view_dependency` scan can observe this dangling view
    and fail while resolving its missing base table.
    
    This change drops `uqv1` after its last assertion and before dropping
    its base tables, so the case does not expose an invalid intermediate
    state to concurrently running regression suites.
---
 regression-test/suites/query_p0/join/test_join5.groovy | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/regression-test/suites/query_p0/join/test_join5.groovy 
b/regression-test/suites/query_p0/join/test_join5.groovy
index 4323575870f..fe2f629ca86 100644
--- a/regression-test/suites/query_p0/join/test_join5.groovy
+++ b/regression-test/suites/query_p0/join/test_join5.groovy
@@ -101,6 +101,8 @@ suite("test_join5", "query,p0") {
             where f2 = 53;
         """
 
+    // Avoid exposing a dangling view to concurrent information_schema scans.
+    sql "DROP VIEW IF EXISTS ${tbName7};"
     sql "DROP TABLE IF EXISTS ${tbName4};"
     sql "DROP TABLE IF EXISTS ${tbName5};"
     sql "DROP TABLE IF EXISTS ${tbName6};"


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to