zhangshenghang commented on issue #10350: URL: https://github.com/apache/seatunnel/issues/10350#issuecomment-3756857459
<!-- code-pr-reviewer --> **Thank you for reporting this.** I've checked the codebase and can confirm the inconsistency in `nullable` option handling across connectors. - `CsvReadStrategy.readProcess` validates nullability when missing columns are encountered (in `seatunnel-connectors-v2/connector-file/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/source/reader/CsvReadStrategy.java`) - S3 and SFTP connectors reuse the same base class, so they should behave similarly - Other connectors (e.g., JDBC, Kafka) don't enforce nullable constraints at read time, only during schema initialization To help us reproduce and fix this efficiently, could you clarify: 1. Which specific connectors did you observe ignoring the `nullable` option? 2. What is the expected vs actual behavior (e.g., error on null vs null values accepted)? 3. Could you provide a minimal sample config and data file that demonstrates the issue? -- 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]
