hyoj-dev opened a new pull request, #12090:
URL: https://github.com/apache/seatunnel/pull/12090

   ### Purpose of this pull request
   
   Related to #11007.
   
   This PR moves deterministic Aerospike sink `data_format` validation into 
`AerospikeSinkFactory.optionRule()` so invalid values are rejected during 
factory validation instead of later when the writer processes a record.
   
   The validation accepts `map`, `string`, and `kv` case-insensitively. The 
existing default and all valid configurations remain unchanged. Network, 
server, schema-dependent, and record-dependent checks remain at runtime.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. An unsupported `data_format` is now rejected earlier during factory 
configuration validation. Supported values, case-insensitive behavior, and the 
default value remain unchanged.
   
   ### How was this patch tested?
   
   Added focused factory validation tests covering:
   
   - all supported `data_format` values;
   - case-insensitive values;
   - an unsupported value; and
   - the default value when `data_format` is omitted.
   
   ```shell
   ./mvnw -pl seatunnel-connectors-v2/connector-aerospike \
     -DskipITs -Dtest=AerospikeFactoryTest test
   
   ./mvnw -pl seatunnel-connectors-v2/connector-aerospike \
     -DskipTests verify
   ```
   
   Result: 4 focused tests passed with no failures or errors. The Aerospike 
connector module verification also completed successfully.
   
   ### Check list
   
   * [x] No new Jar binary package is added.
   * [x] No documentation update is required because the documented valid 
values and default remain unchanged.
   * [x] No incompatible-changes entry is required because existing valid 
configurations keep the same behavior.
   * [x] No connector registration, distribution, label, or E2E updates are 
required because this PR only changes configuration validation and focused unit 
tests.
   


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