-
-
Notifications
You must be signed in to change notification settings - Fork 661
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
Connects config doesn't have all configs options #521
Comments
We also have the same problem!!! In AKHU under connector Configuration for "Schema Registry" we can see only those 2 properties regarding schema registry :
other schema registry configurations are missing.
and connector than failes! |
Can you provide the exact connector link please ? |
Hi tchiotludo, I have Kafka and connectors inside secure environment and it's not exposed to outside world. I used debezium base connector: And imported debezium connect plugins, but you can also use debezium connect with plugins: In plugins I added also JMS connect: |
And I also must say, that missing config options are on all connectors. So you can use io.debezium.connector.postgresql.PostgresConnector for testing purposes. |
mostly this one is hardcoded, I don't understand why plugins to expose all the properties. |
AKHQ don't have all configuration properties under configs tab.
For example:
While configuring AVRO Schema Registry for JMS connector in configs section there is no options to configure:
Under configs there should be available all available settings for connectors.
So to configure connector with all necessary properties direct call to connect API is needed.
Example configuration via REST API:
{
"connector.class": "io.macronova.kafka.connect.jms.JmsSinkConnector",
"jms.message.converter.output.format": "avro",
"errors.log.include.messages": "true",
"tasks.max": "1",
"basic.auth.credentials.source": "USER_INFO",
"value.converter.schema.registry.basic.auth.user.info": "user:password",
"jms.destination.name": "queue.from.kafka.avro",
"errors.deadletterqueue.context.headers.enable": "true",
"value.converter.basic.auth.credentials.source": "USER_INFO",
"jms.url": "tcp://url:port,tcp://url:port",
"schema.registry.url": "https://url:8283",
"jms.username": "user",
"errors.deadletterqueue.topic.replication.factor": "3",
"value.converter": "io.confluent.connect.avro.AvroConverter",
"errors.log.enable": "true",
"key.converter": "io.confluent.connect.avro.AvroConverter",
"errors.retry.timeout": "10000",
"topics": "topic-name",
"jms.connection.factory": "com.tibco.tibjms.TibjmsQueueConnectionFactory",
"errors.retry.delay.max.ms": "5000",
"value.converter.schema.registry.url": "https://url:8283",
"errors.deadletterqueue.topic.name": "que-name",
"name": "name",
"schema.registry.basic.auth.user.info": "user:password",
"errors.tolerance": "all",
"jms.password": "password",
"jms.destination.type": "queue",
"key.converter.schema.registry.url": "https://url:8283"
}
The text was updated successfully, but these errors were encountered: