debezium/dbz#1098 Add Qdrant connection validator by gmarav05 · Pull Request #280 · debezium/debezium-platform

gmarav05 · 2026-03-03T17:55:10Z

Adds Qdrant Sink Connection Validator DBZ-9441

Summary

This PR adds support for validating Qdrant Sink connections.

Changes

Implements QdrantConnectionValidator for checking connectivity to Qdrant.
Adds QDRANT type to ConnectionEntity.Type enum.
Updates connection-schemas.json with Qdrant connection schema.
Added integration test for Qdrant connection validation.

Testing:

It also includes integration tests for both valid and invalid Qdrant connection configurations.

Fixes debezium/dbz#1098 DBZ-9441

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

...r/src/test/java/io/debezium/platform/environment/connection/QdrantConnectionValidatorIT.java

jpechane · 2026-03-04T05:27:19Z

debezium-platform-conductor/src/main/resources/connection-schemas.json

+          "title": "Protocol to use (http or https)",
+          "default": "http"
+        },
+        "apiKey": {


Where is apiKey used?

Currently, the apiKey property is not used in the validator implementation.

I included it in the schema for future support of Qdrant API key authentication, but since it is not being used, We can remove it to avoid confusion.

Let me know if you prefer it removed or if you would like me to add support for API key in the validator.

If possible I'd prefer to add the support. Also if you can rename it to api.key.

@mfvitale Do you agree?

Yeah sure no problem I will add support, I will wait for the approval.

Yes, we should add support also for api.key

If possible I'd prefer to add the support. Also if you can rename it to api.key.

@mfvitale Do you agree?

yeah sure @jpechane @mfvitale , I will add support for the api.key property in the validator and update the schema accordingly.

mfvitale · 2026-03-04T15:05:37Z

debezium-platform-conductor/src/main/java/io/debezium/platform/data/model/ConnectionEntity.java

        RABBITMQ_STREAM,
        RABBITMQ_NATIVE_STREAM,
        MILVUS,
+        @JsonProperty("QDRANT")


Could you clarify why you added the annotation here?

yeah sure, I added the "QDRANT" annotation for consistency with other enum values that use custom JSON names.

If it is not needed for Qdrant, I can remove it.

mfvitale · 2026-03-04T15:07:44Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+    @Override
+    public ConnectionValidationResult validate(Connection connectionConfig) {
+        Map<String, Object> config = connectionConfig.getConfig();
+        String host = (String) config.getOrDefault("host", "localhost");


Could you reason why localhost should be a good default here?

Okay So localhost was used as a default to allow local development and testing out of the box.

I am planning to remove that.

mfvitale · 2026-03-04T15:11:23Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+            URL url = new URL(healthEndpoint);
+            HttpURLConnection conn = (HttpURLConnection) url.openConnection();
+            conn.setRequestMethod("GET");
+            conn.setConnectTimeout(3000);


Could you add a configuration property for these timeouts like in

debezium-platform/debezium-platform-conductor/src/main/java/io/debezium/platform/environment/connection/destination/KafkaConnectionValidator.java

Line 56 in 630a918

public KafkaConnectionValidator(@ConfigProperty(name = "destinations.kafka.connection.timeout") int defaultConnectionTimeout) {

?

yeah sure i started working on this I will refactor the validator to use a configuration property for timeouts, similar to the Kafka validator, to allow users to customize connection timeouts.

thanks for the reference!

mfvitale · 2026-03-04T15:16:02Z

debezium-platform-conductor/src/main/resources/connection-schemas.json

+        "protocol": {
+          "type": "string",
+          "title": "Protocol to use (http or https)",
+          "default": "http"


This is currently not supported but it is an interesting idea.

Currently, the protocol property is not supported, but I agree it is a useful idea.

I can leave it in the schema for future support or remove it for now, based on your preference @jpechane @mfvitale.

I prefer to remove it to avoid confusion.

yeah sure i will remove this asap.

gmarav05 · 2026-03-10T17:37:57Z

Hi @jpechane @mfvitale, Could you please take another look and Re run the CI.

mfvitale · 2026-03-11T09:47:51Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+        }
+
+        String apiKey = getString(config, API_KEY);
+        String healthEndpoint = protocol + "://" + host + ":" + port + "/healthz";


WDYT to define a endpoint format string and the use "".formatted to pass the parameters?

I think this is a great idea, I will update the validator to define health endpoint format constant and switch to .formatted(host, port) when building the URL for clarity and maintainability.

mfvitale · 2026-03-11T09:52:12Z

...r/src/test/java/io/debezium/platform/environment/connection/QdrantConnectionValidatorIT.java

+public class QdrantConnectionValidatorIT {
+
+    @Test
+    public void testValidate_withValidConfig_shouldReturnSuccessOrFailure() {


Well effectively this is not a meaningful test. You shoul start a qdrant container and test the real connectivity. I suggest to have a look to what has been done with AzureEventHubsTestResource

Thanks for the suggestion. I now replaced the previous Qdrant IT with a real Testcontainers based integration test and added a dedicated QdrantTestResource just like AzureEventHubsTestResource.

The test now validates connectivity against a running Qdrant container using the actual mapped host/port.

mfvitale · 2026-03-12T09:44:52Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+            URL url = new URL(healthEndpoint);
+            HttpURLConnection conn = (HttpURLConnection) url.openConnection();
+            conn.setRequestMethod("GET");
+            conn.setConnectTimeout((int) Duration.ofSeconds(defaultConnectionTimeout).toMillis());
+            conn.setReadTimeout((int) Duration.ofSeconds(defaultConnectionTimeout).toMillis());
+            if (!isBlank(apiKey)) {
+                conn.setRequestProperty("api-key", apiKey);
+            }
+            int responseCode = conn.getResponseCode();
+            if (responseCode == 200) {
+                return ConnectionValidationResult.successful();
+            }
+            return ConnectionValidationResult.failed("Qdrant health check failed with status: " + responseCode);


maybe you could wrap this into a method?

yeah sure Thank you for the feedback @mfvitale

mfvitale

Hi @gmarav05 Overall it LGTM. I just left a minor comment.

jpechane

@gmarav05 I left last minor comment, when addressed we are good to go.

jpechane · 2026-03-12T10:06:35Z

...r/src/test/java/io/debezium/platform/environment/connection/QdrantConnectionValidatorIT.java

+    }
+
+    @Test
+    public void testValidate_withValidConfig_shouldReturnSuccess() {


Please don't use undersocres in identifier

yeah sure i will make changes to this and update it. thank you @jpechane

gmarav05 · 2026-03-19T16:23:43Z

@gmarav05 I left last minor comment, when addressed we are good to go.

Sure, Sorry for the delay I had emergency. I was not active. I will start working.

gmarav05 · 2026-03-19T16:46:47Z

hello @jpechane , @mfvitale. Can you please review my PR. Please let me know if any changes are required I mostly fixed all the issues from feedback.

mfvitale · 2026-03-20T08:02:25Z

@gmarav05 Could you please rebase with main?

gmarav05 · 2026-03-20T08:08:00Z

@gmarav05 Could you please rebase with main?

yeah sure @mfvitale .

github-actions · 2026-03-20T08:53:55Z

Hi @gmarav05, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

mfvitale · 2026-03-20T10:19:18Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+        }
+    }
+
+    private static String getString(Map<String, Object> config, String key) {


Could you use the method that are now in ConnectionConfigUtils?

mfvitale · 2026-03-20T11:01:11Z

debezium-platform-conductor/src/main/resources/connection-schemas.json

      "type": "object",
      "required": [
-        "host",
+        "hostname",


Seems this is not correct.

Ooops I will fix it asap.

This change should not be there.

jpechane · 2026-03-23T10:34:37Z

.../java/io/debezium/platform/environment/connection/destination/QdrantConnectionValidator.java

+        }
+
+        Integer port = ConnectionConfigUtils.getInteger(config, PORT);
+        if (port == null || port <= 0) {


@mfvitale Doesn't ignoring of negative port go against the validation prnicpile?

Good point. Yes, we should avoid putting defaults. This is something that could be done by the UI if we want but for sure not here.

Hello @jpechane , @mfvitale, Thank you for bringing this up. I have updated the validator to return a failure instead of defaulting to port 6333. Defaults should be handled by the UI, not the validator. by adding this return ConnectionValidationResult.failed("Port must be specified and must be a positive number for Qdrant connection"); WDYT.

jpechane

@gmarav05 @mfvitale I left one question. When answered/addresed this is good to go.

gmarav05 · 2026-03-24T07:12:25Z

@gmarav05 @mfvitale I left one question. When answered/addresed this is good to go.

Hello @jpechane. I have locally updated the validator to return a failure instead of defaulting to port 6333. Defaults should be handled by the UI, not the validator. by adding this return ConnectionValidationResult.failed("Port must be specified and must be a positive number for Qdrant connection"); Please let me know if this is correct approach.

mfvitale · 2026-03-24T10:04:42Z

@gmarav05 Could you please rebase with latest changes on main?

Signed-off-by: Aravind <gmarav005@gmail.com>

Qdrant connection validator Signed-off-by: Aravind <gmarav005@gmail.com>

Signed-off-by: Aravind <gmarav005@gmail.com>

test Signed-off-by: Aravind <gmarav005@gmail.com>

…ator Signed-off-by: Aravind <gmarav005@gmail.com>

Signed-off-by: Aravind <gmarav005@gmail.com>

…of defaulting Signed-off-by: Aravind <gmarav005@gmail.com>

gmarav05 · 2026-03-24T12:21:19Z

@gmarav05 Could you please rebase with latest changes on main?

Yeah sure @mfvitale , I rebased it now with main.

mfvitale · 2026-03-26T08:41:15Z

@gmarav05 one last this to fix and then this could be merged.

…is host key Signed-off-by: Aravind <gmarav005@gmail.com>

gmarav05 · 2026-03-26T09:22:54Z

@gmarav05 one last this to fix and then this could be merged.

I have now fixed that in schema. Thank you @mfvitale

mfvitale · 2026-03-26T10:51:07Z

@gmarav05 LGTM. When CI passes it can be merged

mfvitale · 2026-03-26T11:02:46Z

@gmarav05 Applied, thanks!

Naros requested changes Mar 3, 2026

View reviewed changes

Naros approved these changes Mar 4, 2026

View reviewed changes

jpechane reviewed Mar 4, 2026

View reviewed changes

mfvitale reviewed Mar 4, 2026

View reviewed changes

gmarav05 requested review from jpechane and mfvitale March 9, 2026 08:30

mfvitale reviewed Mar 11, 2026

View reviewed changes

mfvitale reviewed Mar 12, 2026

View reviewed changes

jpechane reviewed Mar 12, 2026

View reviewed changes

gmarav05 force-pushed the dbz-1098-Qdrant-sink-connection-validator branch from 0e71677 to 80a1ad5 Compare March 19, 2026 16:37

mfvitale approved these changes Mar 19, 2026

View reviewed changes

gmarav05 force-pushed the dbz-1098-Qdrant-sink-connection-validator branch from a7cb1a5 to 039b501 Compare March 20, 2026 09:06

mfvitale reviewed Mar 20, 2026

View reviewed changes

gmarav05 force-pushed the dbz-1098-Qdrant-sink-connection-validator branch from f168fd6 to bd58189 Compare March 20, 2026 11:03

jpechane reviewed Mar 23, 2026

View reviewed changes

gmarav05 added 8 commits March 24, 2026 17:49

debezium/dbz#1098 Add Qdrant connection validator

514d56c

Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Add copyright headers

2b8059c

Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Address review feedback for

6984908

Qdrant connection validator Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Fix compilation error in QdrantConnectionValidator

365486c

Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 add container-backed integration

2cf035d

test Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Address review feedback for Qdrant connection valid…

091d759

…ator Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Use ConnectionConfigUtils in QdrantConnectionValidator

f3693e2

Signed-off-by: Aravind <gmarav005@gmail.com>

debezium/dbz#1098 Fail validation on missing or invalid port instead …

e5653a5

…of defaulting Signed-off-by: Aravind <gmarav005@gmail.com>

gmarav05 force-pushed the dbz-1098-Qdrant-sink-connection-validator branch from b6507ac to e5653a5 Compare March 24, 2026 12:19

jpechane approved these changes Mar 26, 2026

View reviewed changes

mfvitale requested changes Mar 26, 2026

View reviewed changes

debezium/dbz#1098 Add RabbitMQ stream connection schema and align Red…

6959e97

…is host key Signed-off-by: Aravind <gmarav005@gmail.com>

gmarav05 requested a review from mfvitale March 26, 2026 09:15

mfvitale merged commit 03164b7 into debezium:main Mar 26, 2026
7 checks passed

Uh oh!

Conversation

gmarav05 commented Mar 3, 2026

Adds Qdrant Sink Connection Validator DBZ-9441

Summary

Changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mfvitale Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gmarav05 commented Mar 10, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mfvitale left a comment

Choose a reason for hiding this comment

Uh oh!

jpechane left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gmarav05 commented Mar 19, 2026

Uh oh!

gmarav05 commented Mar 19, 2026

Uh oh!

mfvitale commented Mar 20, 2026

Uh oh!

gmarav05 commented Mar 20, 2026

Uh oh!

github-actions bot commented Mar 20, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mfvitale Mar 4, 2026 •

edited

Loading

mfvitale Mar 26, 2026 •

edited

Loading

gmarav05 commented Mar 24, 2026 •

edited

Loading

mfvitale commented Mar 24, 2026 •

edited

Loading