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

PostgreSQL missing metadata info

    XMLWordPrintable

Details

    Description

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      It looks like the documentation for the PostgreSQL connector is not up to date. This https://debezium.io/documentation/reference/1.9/connectors/postgresql.html#postgresql-meta-information meta information block seems no more returned. Also, the same info is already present in the block `source`.

      What Debezium connector do you use and what version?

      PostgreSQL 1.9.6

      What is the connector configuration?

      "connector.class": "io.debezium.connector.postgresql.PostgresConnector",
      "tasks.max": "1",
      "plugin.name": "pgoutput",
      "database.hostname": "postgresql-db",
      "database.port": "5432",
      "database.user": "postgres",
      "database.password": "postgres",
      "database.dbname" : "postgres",
      "database.server.id": "156054",
      "database.server.name": "postgresqldbserver1",
      "database.history.kafka.bootstrap.servers": "broker:29092"

      What is the captured database version and mode of deployment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      Docker postgres 14.1 alpine

      What behaviour do you expect?

      If existent, find the block of metadata info.

      What behaviour do you see?

      The metadata is not there, but same info is in another block.

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      It is also in the new 2.0 documentation.

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      Yes.

      How to reproduce the issue using our tutorial deployment?

      No.

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Update the doc.

      Which use case/requirement will be addressed by the proposed feature?

      None as there is already a define behaviour.

      Implementation ideas (optional)

      None.

      Attachments

        Activity

          People

            broldan@redhat.com Robert Roldan
            dfrancesconi Daniele Francesconi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: