You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to configure schemas for input topics in a Pulsar sink connector, similar to how we can set the schema for output topics in function using outputSchemaType.
I've explored two approaches:
Using sinkConfig.setInputSpecs:
Attempted to set ConsumerConfig
Tried setting the same schema type as used in outputSchemaType via the schemaType field of ConsumerConfig
Using sinkConfig.setTopicToSchemaType:
almost the same procedure as for InputSpecs
Both approaches result in the following schema type mismatch error: Schema type mismatch org.apache.pulsar.client.api.schema.GenericObject vs com.example.dtos.SimpleObject
Questions
Is this expected behavior? Can we only set custom schemas (classes implementing the schema interface) on output topics?
If it is possible to set input topic schemas, what's the correct approach?
Additional Context
This is the Schema that I am using (kept it simple for demo purposes):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to configure schemas for input topics in a Pulsar sink connector, similar to how we can set the schema for output topics in function using
outputSchemaType
.I've explored two approaches:
Using
sinkConfig.setInputSpecs
:Using
sinkConfig.setTopicToSchemaType
:Both approaches result in the following schema type mismatch error:
Schema type mismatch org.apache.pulsar.client.api.schema.GenericObject vs com.example.dtos.SimpleObject
Questions
Additional Context
This is the Schema that I am using (kept it simple for demo purposes):
Beta Was this translation helpful? Give feedback.
All reactions