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

message size is at least 68x larger for changes with bit varying columns

    Details

    • Steps to Reproduce:
      Hide
      1. create table dbz_test (id integer primary key, bvc_test bit varying);
      2. add table to whitelist
      3. insert into dbz_test values(1,'1');
      4. note error : ERROR WorkerSourceTask{id=debezium-0} failed to send record to dbz.public.dbz_test: {} (org.apache.kafka.connect.runtime.WorkerSourceTask:329)
        org.apache.kafka.common.errors.RecordTooLargeException: The message is 357914344 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration. 
      Show
      create table dbz_test (id integer primary key, bvc_test bit varying); add table to whitelist insert into dbz_test values(1,'1'); note error : ERROR WorkerSourceTask{id=debezium-0} failed to send record to dbz.public.dbz_test: {} (org.apache.kafka.connect.runtime.WorkerSourceTask:329) org.apache.kafka.common.errors.RecordTooLargeException: The message is 357914344 bytes when serialized which is larger than the maximum request size you have configured with the max.request.size configuration. 

      Description

      this is most likely due to changes for DBZ-1949

      with v1.0.3.Final, this is not an issue and the message size is <= 5MB (
      max.request.size=5242880)
       
      now with v1.2.0.Final, message size is ~341MB (357914344 bytes)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rkerner René Kerner
                Reporter:
                dajerome David Jerome
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: