zddr opened a new pull request, #49961:
URL: https://github.com/apache/doris/pull/49961

   ### What problem does this PR solve?
   
   Here’s the translated content in a clean Markdown format:
   
   ---
   
   #### **Current Situation**
   The user-configured `excluded_trigger_tables` is split by commas into a 
`Set<String> excludedTriggerTables`.  
   During materialized view (MV) refresh checks, the system compares table 
snapshots. If `excludedTriggerTables.contains(tableName)` matches, the table is 
skipped for refresh.
   
   #### **Problem**
   The current logic cannot distinguish between tables with identical names 
under different catalogs or databases.
   
   #### **Solution**
   Change the configuration format to `[catalog_name.][db_name.]table_name`:
   1. **No catalog/db prefix**: Behaves identically to the current 
implementation (matches any table with the same name).
   2. **With catalog/db prefix**: Requires full match of 
`catalog_name.db_name.table_name` for exclusion.
   3. **Backward compatibility**: Existing configurations (plain `table_name`) 
remain valid without metadata migration.
   
   #### **Example**
   **MV Definition:**
   ```sql
   CREATE MV mv1 AS 
   SELECT * FROM ctl1.db1.t1 
   JOIN ctl1.db1.t2 
   JOIN ctl1.db2.t1 
   JOIN ctl2.db1.t1;
   ```
   
   **Behavior by Configuration:**
   1. `t1` → Skips: `ctl1.db1.t1`, `ctl1.db2.t1`, `ctl2.db1.t1`  
   2. `db1.t1` → Skips: `ctl1.db1.t1`, `ctl2.db1.t1`  
   3. `ctl1.db1.t1` → Skips only: `ctl1.db1.t1`  
   
   
   Issue Number: close #xxx
   
   Related PR: #xxx
   
   Problem Summary:
   Exclude trigger table support db and catalog
   ### Release note
   Exclude trigger table support db and catalog
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
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: commits-unsubscr...@doris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to