docs: Highlight view+index in debezium pages and lower prominence for Postg… #29150
Conversation
| identifier: "mysql-dbz" | ||
| --- | ||
|
|
||
| {{< tip >}} | ||
| - As an alternative to using Kafka and Debezium, Materialize also provides | ||
| native support for MySQL. |
There was a problem hiding this comment.
Once we sort out our docs frontmatter so that there is a landing page under Ingest data/MySQL/, we can update this to link there.
| identifier: "pg-dbz" | ||
| --- | ||
|
|
||
| {{< tip >}} | ||
| - As an alternative to using Kafka and Debezium, Materialize also provides | ||
| native support for PostgreSQL. |
There was a problem hiding this comment.
Once we sort out our docs frontmatter so that there is a landing page under Ingest data/PostgreSQL/, we can update this to link there.
kay-kim
changed the title
kay-kim
force-pushed
the
docs-debezium-tweaks
branch
from
2eede60
to
9e53d74
Compare
| Materialize, [indexes](/concepts/indexes/) on a view maintain view results in | ||
| memory within a [cluster](/concepts/clusters/ "pools of compute resources (CPU, | ||
| memory, and scratch disk space)"). As the underlying data changes, indexes | ||
| **incrementally update** the view results in memory. |
There was a problem hiding this comment.
Once #29090 is merged, will also sprinkle some links to the usage patterns section in this page.
There was a problem hiding this comment.
Can we make the changes to the dbt documentation in a separate PR?
|
Not sure about this approach to de-emphasize Debezium. I was thinking we could either just leave it as is, but rephrase the introduction of each page to highlight that native connectors exist (mostly for scenarios where someone lands on the Kafka + Debezium page from a web search), or add a single "Using Kafka and Debezium" under |
kay-kim
force-pushed
the
docs-debezium-tweaks
branch
from
d90a0a5
to
8740816
Compare
| --- | ||
| title: "PostgreSQL" | ||
| description: "Connect and ingest data from PostgreSQL." | ||
| --- |
There was a problem hiding this comment.
Later on, may use a section template in the docs, but for this work, just using the regular single page template.
kay-kim
force-pushed
the
docs-debezium-tweaks
branch
from
7ac06a5
to
c8e6b66
Compare
|
Also, I can just close this PR (unless the work on that will take a while). |
morsapaes
force-pushed
the
docs-debezium-tweaks
branch
2 times, most recently
from
eea3d67
to
3a66e9c
Compare
doc/user/layouts/shortcodes/ingest-data/ingest-data-kafka-debezium-index.md
Outdated
Show resolved
Hide resolved
doc/user/layouts/shortcodes/ingest-data/ingest-data-kafka-debezium-index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Sorry for the delay here, @kay-kim! Ended up pushing my local changes to your branch, along with some new stuff (like an overview page for both MySQL and PostgreSQL). Also tentatively removed Kafka + Debezium from the dropdowns for MySQL and PostgreSQL, since that could still leave room for confusion; let's just mention Debezium for databases that aren't natively supported, and in context in the Kafka source reference page.
Can you just remove the edits to the dbt page? We should handle that in a separate PR, since this one snowballed into something bigger than just replacing the use of materialized views with indexed views.
…reSQL and MySQL kafka+deb pages
Co-authored-by: Marta Paes <marta.paes.moreira@gmail.com>
kay-kim
force-pushed
the
docs-debezium-tweaks
branch
from
52850a0
to
f5a90ea
Compare
…reSQL and MySQL kafka+deb pages
Moved PostgreSQL/MySQL kafka+deb pages to Appendix