zhangshenghang opened a new pull request, #11469:
URL: https://github.com/apache/seatunnel/pull/11469

   ## What documentation issues were found
   
   Several Chinese File connector reference pages omitted configuration options 
that are implemented in the shared File source/sink option classes and already 
documented in their English counterparts. This left users unable to discover 
filename filters, source parsing controls, and the Excel worksheet row limit.
   
   ## What changed
   
   - Added missing source options for COS File, FTP File, OBS File, and OSS 
Jindo File, including filename filtering, row delimiters, parsing/schema 
settings, compression, encoding, null handling, and modification-time filters 
where supported.
   - Added `sheet_max_rows` to six Chinese File sink pages and explained its 
Excel-only behavior and default of `1048576`.
   
   ## Updated areas
   
   - Chinese source docs: COS File, FTP File, OBS File, OSS Jindo File.
   - Chinese sink docs: COS File, FTP File, Local File, OSS File, OSS Jindo 
File, SFTP File.
   
   English and Chinese pages were both checked. The English pages already 
documented these options, so this PR updates only the missing Chinese reference 
content.
   
   ## Duplicate PR check
   
   I reviewed Apache SeaTunnel PRs created during the previous seven days 
(2026-07-09 through 2026-07-16), including all documentation-labelled PRs. 
Recent work covered S3 credential providers, CDC recipes, transform recipes, 
and connector feature documentation; none covered these Chinese File connector 
option gaps.
   
   ## Verification
   
   - `./mvnw spotless:apply`
   - `./mvnw -q -DskipTests verify`
   - `npx --yes [email protected] -c .dlc.json -q` for all 10 changed 
Markdown files
   - `git diff --check`


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