Aryadeepta opened a new pull request, #11964:
URL: https://github.com/apache/seatunnel/pull/11964
### Purpose of this pull request
Migrate declarative-eligible Cassandra connector configuration validation to
`OptionRule` / `Conditions` as part of #11007.
This change:
- adds declarative non-blank validation for required Cassandra source and
sink options
- validates source `cql` when configured
- validates `tables_configs` as non-empty and ensures each nested entry
contains a non-blank `cql`
- validates Cassandra consistency levels declaratively
- validates Cassandra sink batch types declaratively
- preserves the existing `cql` / `tables_configs` exclusivity
- preserves username/password bundling
Cassandra-dependent validation such as connectivity, authentication, schema
discovery, CQL execution, duplicate resolved tables, and sink target-field
validation remains in the existing runtime paths.
### Does this PR introduce _any_ user-facing change?
Yes.
Invalid static Cassandra configurations that can be validated without
connecting to Cassandra are now rejected earlier through declarative
`OptionRule` validation with `OptionValidationException`.
Runtime validation that depends on Cassandra state remains unchanged.
### How was this patch tested?
Added and ran focused `ConfigValidator` unit tests covering positive and
negative source/sink validation cases.
```text
./mvnw test \
-pl seatunnel-connectors-v2/connector-cassandra \
-Dtest=CassandraFactoryTest \
-DfailIfNoTests=false
```
Result: 20 tests passed.
Also verified Spotless and `git diff --check`.
### Check list
* [x] No new Jar binary package is added.
* [x] No connector registration/plugin mapping changes are required because
this modifies an existing connector.
* [x] No incompatible configuration option is introduced or removed.
* [x] Unit tests cover the declarative validation changes.
Related #11007
--
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]
