Hi, I am trying to push my source postgres cdc changes to target oracle tables through kafka and that's why using debezium kafka source connector(docker image debezium/connect:1.8) as a source connector and kafka jdbc sink connector as a sink connector. along with kafka broker. Now, I want the topic names to be created in capital letters as otherwise we face other issues while creating the tables in oracle through the jdbc sink connector. As the postgres tables are by default created in small letters , I am using the below configurations in my source connector to create the topic in capital letters(hardcoding) and the below is working fine. Now, I want this to be done for multiple tables, "table.include.list": prodfxiapp1.requests,prodfxiapp1.trade,prodfxiapp1.leg. Is it possible to do it through the config changes? If so, what should be the changes?

"name": "source-connector",
"config": {
"connector.class": "io.debezium.connector.postgresql.PostgresConnector",
"tasks.max": "1",
"database.hostname": "",
"database.port": "",
"database.user": "",
"database.password": "",
"database.dbname": "",
"database.server.name": "",
"table.include.list": "prodfxiapp1.requests",
"transforms": "topicRename",
"transforms.topicRename.type": "org.apache.kafka.connect.transforms.RegexRouter",
"transforms.topicRename.regex": "(.*)",
"transforms.topicRename.replacement": "REQUESTS"
}

I pushed 9540910 as a work-around, hard-coding the base URL into the Disqus include for now.

That way, the comment widgets are loaded again, but ideally we won't have the base URL in any template/include. With Awestruct, the base URL was part of the environment-specific configuration and could be referenced in templates as a variable then. Is something similar doable for Jekyll?

@mdrillin @indraraj @uidoyen

Hello, My organization is using Sybase ASE 16 SP04 for storing all the transaction and reference data. We have a need to capture and stream the changed data fields on specific data tables as events to the downstream systems. I looked into your documentation, but I don't see Sybase in the support databases list. Do you have a plan to support Sybase database?

Note: I have seen few threads in stackoverflow looking for Sybase ASE connectors for similar need.

Let me know when can you support this and be part of the roadmap.

Regards,
Nazimuddin
Enterprise Architect - Carelon Inc (a Elevance Health company)

See selector at upper right on http://localhost:4000/releases/1.3/; let's put the newest first, matching what's done by Antora in the docs.

@mdrillin @uidoyen @indra

Atm. all the blog post AsciiDoc files have the same footer ("About Debezium", "Get Involved"). This should be extracted into the template. Might also go under the author info actually.

@mdrillin @indraraj @uidoyen Here's a first follow-up improvement.

Hello, My organization is using Sybase ASE 16 SP04 for storing all the transaction and reference data. We have a need to capture and stream the changed data fields on specific data tables as events to the downstream systems. I looked into your documentation, but I don't see Sybase in the support databases list. Do you have a plan to support Sybase database?

Note: I have seen few threads in stackoverflow looking for Sybase ASE connectors for similar need.

Let me know when can you support this and be part of the roadmap.

Regards,
Nazimuddin
Enterprise Architect - Carelon Inc (a Elevance Health company)

Link to http://localhost:4000/blog.atom from the blog page is broken.

@mdrillin @indraraj @uidoyen

When hovering over the Debezium logo, that tile gets a bit darker. That's not the case when hovering over any of the menu items ("Blog", "Community", etc.). This should be done consistently. The hover state should be a bit lighter than the active state when being e.g. on the blog URL.

Hello,
I'm following the steps from that documentation https://debezium.io/documentation/reference/operations/openshift.html (adapting to my minikube environment)
It seems to me that a step is missing (or I am misunderstanding something), in step "3.c", it is described how to create an image for connect named ${DOCKER_ORG}/connect-debezium, and shortly after stating we should see a pod

debezium-connect-3-4sdjr                   1/1       Running       0          1m

... without describing how that pod is created, so I guess there's a missing step to create a deployment based on the built docker image, no?

Akin to the GA snippet.

@mdrillin @uidoyen @indraraj

Did we have one before? I don't think we should use the Fedora, as this is an upstream project website, not a Red Hat property (the Fedora is fine in the header and footer, as it's about the sponsoring relationship there).

@mdrillin @uidoyen @indraraj

I suppose simplest would be to actually do call bundle update and bundle install in the Dockerfile of the builder image, so that the actual build itself should be quicker.

@uidoyen

Currently it seems like it's completely separate HTML page. Same for license.html.

@mdrillin @indraraj @uidoyen

In order to preview how the website looks like in the course of the migration, set up a GH Action which builds and publishes the website to somerepo.github.io. In the future, we should use this to publish a staged preview of the website before pushing changes to the live website.

Also the current dev and stable versions in the Jumbotron are hard-coded, whereas I think this was data-driven with Awestruct.

@mdrillin @indraraj @uidoyen

Need to investigate if we can move away from the excerpt marker (+++<!-- more -->+++) in the blog post and can still display the blog summary with HTML formatting.

An area for improvement of the blog is discoverability of earlier posts. Right now, you only can go to older posts via the "Older" link at the bottom of the list page. To mitigate that, we added the "Featured Posts" section on the left some time ago, which is driven by the "Featured" tag assigned to posts. But it'd be nice to have some sort of "archive" side bar, as done on many blogs. Is here something like that in Jekyll we could use?

@mdrillin @indraraj @uidoyen

I created a docker-compose file and run it. It works fine but when I get inside the containers no command works. even apt-get or apt, it gives only command not found error. I dont know why?

in mac os intel.
docker version: 20.10.13

version: '2'
services:
  zookeeper:
    image: debezium/zookeeper
    ports:
      - 2181:2181
      - 2888:2888
      - 3888:3888
  kafka:
    image: debezium/kafka
    ports:
      - 9092:9092
    environment:
      - ZOOKEEPER_CONNECT=zookeeper:2181
  postgres:
    container_name: postgresql
    image: debezium/postgres:11
    ports:
      - 5432:5432
    environment:
      - POSTGRES_DB=debezium
      - POSTGRES_USER=user
      - POSTGRES_PASSWORD=password
  connect:
    image: debezium/connect
    ports:
      - 8083:8083
      - 5005:5005
    environment:
      - BOOTSTRAP_SERVERS=kafka:9092
      - GROUP_ID=1
      - CONFIG_STORAGE_TOPIC=my_connect_configs
      - OFFSET_STORAGE_TOPIC=my_connect_offsets
      - STATUS_STORAGE_TOPIC=my_source_connect_statuses

CONTAINER ID   IMAGE                  COMMAND                  CREATED          STATUS         PORTS                                                                    NAMES
a34e34516bdf   debezium/kafka         "/docker-entrypoint.…"   9 minutes ago    Up 8 minutes   0.0.0.0:9092->9092/tcp                                                   docker-kafka-1
1500945fd17c   debezium/connect       "/docker-entrypoint.…"   21 minutes ago   Up 8 minutes   0.0.0.0:5005->5005/tcp, 0.0.0.0:8083->8083/tcp, 9092/tcp                 docker-connect-1
d475c9993513   debezium/zookeeper     "/docker-entrypoint.…"   21 minutes ago   Up 8 minutes   0.0.0.0:2181->2181/tcp, 0.0.0.0:2888->2888/tcp, 0.0.0.0:3888->3888/tcp   docker-zookeeper-1
58896bc0547b   debezium/postgres:11   "docker-entrypoint.s…"   4 hours ago      Up 8 minutes   0.0.0.0:5432->5432/tcp                                                   postgresql

On the specific version release page, the documentation button always links to the latest stable version of the documentation. It should link to the specific version, not the latest stable

README and license.txt say Apache v2, but badge in README says CC.

@mdrillin @uidoyen @indraraj I think with Awestruct we fed things through a miminizer (removing newlines etc.), if you look at the source of the current live website.

On https://debezium.io/releases/, we show older to newer for the current series, but then newer to older under "See older releases". We should consistently do the latter, i.e. switch the order for the current releases.

Also, in the menu for Documentation and Releases on the left, we have two different green badges for "Stable" and "Latest Stables", but we only show "Stable" on the actual https://debezium.io/releases/ and https://debezium.io/documentation/ pages themselves. Let's add the "Latest Stable" distinction there, too.

Before we moved to Antora, there only was a single version published for the documentation, under the /docs path. With the old site, there used to be redirects for URLs like these:

https://debezium.io/docs/tutorial/
https://debezium.io/docs/online-resources/
https://debezium.io/docs/faq/
https://debezium.io/docs/connectors/postgresql/

They got lost in the transition to Jekyll. We should double-check with the old redirect configuration and add back all that are missing, so to keep any links out in the wild intact.

@mdrillin @uidoyen @indraraj

If you check out what ends up in the _site directly, you'll find some Markdown files and the Antora YAML files. They shouldn't be published, as they are build-time only info.

@mdrillin @uidoyen @indraraj

@mdrillin @uidoyen @indra

in the following url:
https://debezium.io/documentation/reference/1.9/connectors/oracle.html
https://debezium.io/documentation/reference/stable/connectors/oracle.html

the follwing is wrong：
ALTER SYSTEM SET archive_log_target=1200 scope=both;

the following is correct ：
ALTER SYSTEM SET archive_lag_target=1200 scope=both;

archive_lag_target is the correct oracle parameter，not archive_log_target！

It still speaks of Awestruct but should describe how to build the site with Jekyll. This should also touch on how to enable a specific environment (e.g. "production").

@uidoyen, would you like to grab this one?

As discussed with @uidoyen; I'd expect Jekyll has built-in support for GA and we just need to configure our tracking id somewhere. If so, the explicit tracker snippet should be removed from the Jekyll counterpart of the template linked below. The GA tracking should only be enabled for the production website.

That URL has a typo ("wit"); the file should be renamed but a redirect be added so to not break existing links to the old URL

See screenshot below, the spacing is a bit off. It's more equal on the current site, also the buttons and the text on the right hand side seem aligned there.

@mdrillin @indraraj @uidoyen

So we can examine the output during dev and staging.

@indraraj @mdrillin @uidoyen

This should go to https://developers.redhat.com/.

@indraraj @mdrillin @uidoyen

See "Features", "Architecture", "FAQ" etc. They should go straight to the stable links (i.e. not 1.3, but /documentation/reference/...)

@uidoyen @indraraj

On the release details page, earlier releases show a label of 'latest stable' - even though they are not the latest stable. Should just show 'stable' except for the real 'latest stable'

I know, I know, it's a super teeny-tiny detail, but can we make the lower left and the upper right pixel of the Favicon transparent? It doesn't look ideal with a dark browser theme atm.

@mdrillin @indraraj @uidoyen

Following the Documentation link from https://debezium.io/releases/1.7/ results in a 404. The same applies to https://debezium.io/documentation/reference/1.8 .

The Documentation link from https://debezium.io/releases/1.6/ works, and then I'm able to jump to 1.7 via the menu footer. It takes me to https://debezium.io/documentation/reference/stable/index.html .

Contributing to the "make earlier posts more accessible" theme, there should be links to go to the previous and next blog posts.

@indraraj @uidoyen @mdrillin