Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-8085

When performing an incremental snapshot, a stream with the signal stream name is being created on my Redis BDB

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.6.1.Final
    • debezium-server
    • None
    • False
    • None
    • False

      I

      What Debezium connector do you use and what version?

      Oracle debezium connector, Version 2.6.1Final

      What is the connector configuration?

      debezium.sink.type=redis
      debezium.sink.redis.message.format=extended
      debezium.sink.redis.address=localhost:12001
      #debezium.sink.redis.password=Redis123
      debezium.sink.redis.memory.limit.mb=10000

      debezium.source.connector.class=io.debezium.connector.oracle.OracleConnector
      debezium.source.log.mining.strategy=online_catalog
      #debezium.source.log.mining.transaction.retention.ms=180000
      debezium.source.database.pdb.name=ORCLPDB1
      debezium.source.offset.storage=io.debezium.storage.redis.offset.RedisOffsetBackingStore
      debezium.source.topic.prefix=rdi
      debezium.source.database.dbname=ORCLCDB
      debezium.source.database.hostname=172.17.0.2
      debezium.source.database.port=1521
      debezium.source.database.user=c##dbzuser
      debezium.source.database.password=dbz
      debezium.source.include.schema.changes=false
      #debezium.source.log.mining.query.filter.mode=in
      #debezium.source.skip.messages.without.change=true
      debezium.source.table.include.list=C##DBZUSER.TEST
      debezium.source.offset.flush.interval.ms=1000
      debezium.source.tombstones.on.delete=false
      debezium.source.schema.history.internal=io.debezium.storage.redis.history.RedisSchemaHistory
      #debezium.source.internal.log.mining.read.only=true
      #debezium.source.schema.history.internal.store.only.captured.tables.ddl=true
      #debezium.source.log.mining.batch.size.min=100000
      #debezium.source.log.mining.batch.size.max=100000
      #debezium.source.log.mining.batch.size.default=100000
      #debezium.source.key.converter.schemas.enable=false
      #debezium.source.value.converter.schemas.enable=false
      debezium.source.decimal.handling.mode=double
      debezium.source.signal.data.collection=ORCLPDB1.C##DBZUSER.DEBEZIUM_SIGNAL

      debezium.transforms=AddPrefix
      debezium.transforms.AddPrefix.type=org.apache.kafka.connect.transforms.RegexRouter
      debezium.transforms.AddPrefix.regex=.*
      debezium.transforms.AddPrefix.replacement=data:$0
      #quarkus.log.category.*=TRACE
      #quarkus.log.category."io.debezium.connector.oracle.logminer.LogMinerHelper".level=TRACE

      1. The default minimum log level for every log category, change only quarkus.log.level when needed.
        quarkus.log.min-level=trace
      2. The default log level for every log category.
        quarkus.log.level=trace
      1. Determine whether to enable the JSON console formatting extension, which disables "normal" console formatting.
        quarkus.log.console.json=false
      2. The port on which Debezium exposes Microprofile Health endpoint and other exposed status information.
        quarkus.http.port=8088

      ```

      What is the captured database version and mode of deployment?

      Oracle 19c

      What behavior do you expect?

      I wouldn't expect that a stream with the signal name table to be created in the Redis BDB

      What behavior do you see?

      A stream with the signal table name is being created

       

            Unassigned Unassigned
            gali.levin gal levin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: