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

   ## Summary
   
   Small fixes accumulated during a code review of the streaming-job module. 
None of these change runtime semantics for currently-supported scenarios; they 
tighten validation, fix a typo, and harden a concurrent field.
   
   - `StreamingInsertJob.cleanup()`: log was filling `dbId=%s` with 
`getJobId()`. Fix to `getDbId()`.
   - `StreamingInsertJob.getShowSQL()`: typo `TO DATABSE` → `TO DATABASE` in 
the synthesized SQL shown by SHOW JOBS.
   - `JdbcSourceOffsetProvider.currentOffset`: mark `volatile`. The write in 
`updateOffset()` happens outside `splitsLock` while `hasMoreDataToConsume()` / 
`getShowCurrentOffset()` read it without holding the lock.
   - `DataSourceConfigValidator.isValidValue`: `snapshot_split_size` / 
`snapshot_parallelism` previously only checked null/empty. Reject non-numeric 
and non-positive values up front so users get a clear CREATE-time error instead 
of a context-less `NumberFormatException` at runtime.
   - `CdcStreamTableValuedFunction.validate`: previously only checked 
`jdbc_url` / `type` / `table` / `offset`. Now also rejects missing `database` 
(MySQL), missing `schema` (PostgreSQL), and unsupported `type` values, so the 
error surfaces at TVF parse time rather than later inside `getRemoteDbName`.
   
   ## Test plan
   
   - [x] Added UT cases in `DataSourceConfigValidatorTest` covering positive / 
non-numeric / zero / negative for `snapshot_split_size` and 
`snapshot_parallelism`.
   - [x] Added regression cases in `test_cdc_stream_tvf_mysql.groovy` (missing 
`database` for MySQL, unsupported `type`) and 
`test_cdc_stream_tvf_postgres.groovy` (missing `schema` for PostgreSQL).
   - [ ] Existing streaming-job regression suites still pass.


-- 
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]


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

Reply via email to