-
Bug
-
Resolution: Done
-
Major
-
3.0.0.Alpha2
-
None
-
False
-
None
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.7.0
What is the connector configuration?
{ "connector.class" : "io.debezium.connector.db2as400.As400RpcConnector", "name" : "<connector-name>", "sanitize.field.names" : "true", "tasks.max" : "1", "database.hostname" : "<server>", "database.user" : "<user>", "database.password" : "<password>", "database.port" : "8471", "database.dbname" : "<schema>", "database.schema" : "<schema>", "secure" : false, "poll.interval.ms" : "5000", "table.include.list" : "<schema>.<table>", "snapshot.mode" : "schema_only", "key.converter.schema.registry.url": "http://localhost:8081", "value.converter.schema.registry.url": "http://localhost:8081", "key.converter" : "io.confluent.connect.avro.AvroConverter", "value.converter" : "io.confluent.connect.avro.AvroConverter", "socket.timeout" : "300000", "keep.alive" : "false", "topic.prefix" : "test.cdc.db2", "topic.creation.default.partitions" : 3, "topic.creation.default.replication.factor" : 1, "topic.creation.default.cleanup.policy" : "delete,compact", }
What is the captured database version and mode of deployment?
on-premises
What behavior do you expect?
Properties like "secure" should be taken into account when a connector is created.
What behavior do you see?
The connector takes the default value for properties like secure which are represented in AS400ConnectorConfig.
Do you see the same behaviour using the latest released Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
attached
Implementation ideas
The error was most likely caused by the removal of the method
getJdbcConfiguration() in Commit 4edab91b.
connectorConfig.getJdbcConfig() in line 71 of As400ConnectorTask seems to only return connector properties which are also defined in the
RelationalDatabaseConnectorConfig class. Therefore, the withDefaults(JdbcConfiguration config) method in As400JdbcConnection only returns default values and not the values set by the user. In the specific config I provided the default for "secure" returns true for secure, which in turn causes the connector to break for non secure connections.