Skip to content

Commit

Permalink
Minor edits
Browse files Browse the repository at this point in the history
  • Loading branch information
Lauren committed Jul 2, 2018
1 parent 93aa4a3 commit 03e6791
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions v2.1/change-data-capture.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ summary: Change data capture (CDC) provides efficient, distributed, row-level ch
toc: false
---

<span class="version-tag">New in v2.1:</span>Stream changes into Apache Kafka using change data capture (CDC). CDC provides efficient, distributed, row-level change subscriptions and can be used to support downstream processing such as reporting, caching, or full-text indexing.
<span class="version-tag">New in v2.1:</span> Change data capture (CDC) provides efficient, distributed, row-level change feeds into Apache Kafka for downstream processing such as reporting, caching, or full-text indexing.

{{site.data.alerts.callout_danger}}
**This feature is under active development** and only works for a targeted a use case. Please [file a Github issue](file-an-issue.html) if you have feedback on the interface.
Expand Down Expand Up @@ -202,18 +202,18 @@ The following are limitations in July 2, 2018 alpha release, and will be address
{{site.data.alerts.end}}
- The CockroachDB core `CHANGEFEED` is not ready for external testing.
- Some intermediate updates on frequently changed rows are never emitted. [#27101]
- Some intermediate updates on frequently changed rows are never emitted.
- Changefeed progress is not exposed to the user.
- The SQL interface is not final and may change.
- Changefeeds only work on tables with a single column family (which is the default for new tables).
- Changefeeds do not work on interleaved tables.
- Many DDL queries (including `TRUNCATE`, `RENAME`, and `DROP`) will cause undefined behavior on a changefeed watching the affected tables.
- Changefeeds cannot be backed up or restored.
- Changefeeds only work on tables with a single [column family](column-families.html) (which is the default for new tables).
- Changefeeds do not work on [interleaved tables](interleave-in-parent.html).
- Many DDL queries (including [`TRUNCATE`](truncate.html), [`RENAME TABLE`](rename-table.html), and [`DROP TABLE`](drop-table.html)) will cause undefined behavior on a changefeed watching the affected tables.
- Changefeeds cannot be [backed up](backup.html) or [restored](restore.html).
- Changefeed behavior under most types of failures/degraded conditions is not yet tuned.
- Changefeed internal buffering does not respect memory use limitations.
- Changefeeds do not scale horizontally or to high traffic workloads.
- Changefeeds use a pull model, but will use a push model in v2.1, lowering latencies considerably.
- Changefeeds are slow on data recently loaded via `RESTORE` or `IMPORT`.
- Changefeeds are slow on data recently loaded via [`RESTORE`](restore.html) or [`IMPORT`](import.html).
- Additional format options will be added, including Avro.
- Additional envelope options will be added, including one that displays the old and new values for the changed row.
- Additional target options will be added, including partitions and ranges of primary key rows.
Expand Down

0 comments on commit 03e6791

Please sign in to comment.