Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulsar force schema fetch on pulsar-client-thread for all schema requiring schema info fetching #2494

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

ozangunalp
Copy link
Collaborator

Fixes #2493

cescoffier
cescoffier previously approved these changes Feb 21, 2024
@@ -115,8 +115,8 @@ public PulsarIncomingChannel(PulsarClient client, Vertx vertx, Schema<T> schema,
.until(m -> closed.get())
.plug(msgMulti -> {
// Calling getValue on the pulsar-client-internal thread to make sure the SchemaInfo is fetched
if (schema instanceof AutoConsumeSchema || schema instanceof KeyValueSchema) {
return msgMulti.onItem().call(msg -> Uni.createFrom().item(msg::getValue));
if (schema.requireFetchingSchemaInfo()) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same mechanism should be used for batch see line 141

Copy link

@marekczajkowski marekczajkowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add same mechanism for batch case

@ozangunalp
Copy link
Collaborator Author

@marekczajkowski thanks for pointing it out. I pushed the fix.

@ozangunalp ozangunalp merged commit 6d7bd15 into smallrye:main Feb 22, 2024
4 checks passed
@ozangunalp ozangunalp added this to the 4.18.0 milestone Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deadlock when using Avro schema with Pulsar connctor
3 participants