chovy-3012 opened a new issue, #13171:
URL: https://github.com/apache/seatunnel/issues/13171

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   ---
   
   ### What happened
   
   When the same `database.table` appears twice in `table_list`, SeaTunnel does 
not reject the config with the duplicate-table error. The duplicate is silently 
accepted and the job runs normally, as if the duplicate entry were intentional.
   
   The intended validation only fires when the list contains **two or more 
redundant entries** (e.g. the same table listed three times). When the list 
contains **exactly one redundant entry**, the check is skipped:
   
   | table_list | Result |
   | --- | --- |
   | `[t1, t1]` | no error (bug) |
   | `[t1, t1, t2]` | no error (bug) |
   | `[t1, t1, t1]` | duplicate error, correctly |
   
   What the user actually gets:
   
   - **Identical duplicate entries**: the job starts and completes normally. 
The table is read only once and the duplicate entry is silently dropped — the 
source keeps one entry per `database.table` — so there is no signal that the 
config was invalid.
   - **Same table listed twice with different settings** (e.g. a different 
`doris.filter.query` or `doris.read.field` per entry): only the **last** entry 
takes effect. The first entry's projection/filter is silently ignored, so the 
job reads a different column/row set than the config describes, with no warning.
   
   **Reproduce:**
   
   1. Create a Doris source config with duplicate `table_list` entries:
   
   ```hocon
   source {
     Doris {
       fenodes = "127.0.0.1:8030"
       username = "root"
       password = ""
       table_list = [
         { database = "test_db", table = "table1" }
         { database = "test_db", table = "table1" }
       ]
     }
   }
   ```
   
   2. Run the job:
   
   ```shell
   sh bin/seatunnel.sh --config config/doris.conf -e local
   ```
   
   3. Expected: fail immediately with the duplicate-table error (see Error 
Exception below).
   
   4. Actual: no error. The job passes config validation and runs as if only 
one `table_list` entry had been configured.
   
   ---
   
   ### SeaTunnel Version
   
   3.1.0
   
   Also present in 2.3.12 and 2.3.13.
   
   ---
   
   ### SeaTunnel Config
   
   ```hocon
   env {
     parallelism = 1
     job.mode = "BATCH"
   }
   
   source {
     Doris {
       fenodes = "127.0.0.1:8030"
       username = "root"
       password = ""
       table_list = [
         { database = "test_db", table = "table1" }
         { database = "test_db", table = "table1" }
       ]
     }
   }
   
   sink {
     Console {}
   }
   ```
   
   ---
   
   ### Running Command
   
   ```shell
   sh bin/seatunnel.sh --config config/doris.conf -e local
   ```
   
   ---
   
   ### Error Exception
   
   No exception is thrown — that is the bug. The job passes config validation 
and runs normally.
   
   For reference, the intended error message (which is correctly thrown when 
the same table is listed three or more times, i.e. two or more redundant 
entries) is:
   
   ```log
   java.lang.IllegalArgumentException: Please configure unique 
`database`.`table`, not allow null/duplicate: [test_db.table1, test_db.table1]
   ```
   
   ---
   
   ### Zeta or Flink or Spark Version
   
   Zeta engine (local mode)
   
   ---
   
   ### Java or Scala Version
   
   Java 11
   
   ---
   
   ### Screenshots
   
   N/A
   
   ---
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ---
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to