diff --git a/src/current/_includes/v24.3/cdc/core-csv.md b/src/current/_includes/v24.3/cdc/core-csv.md index 5e2a49f8f21..0901eed2def 100644 --- a/src/current/_includes/v24.3/cdc/core-csv.md +++ b/src/current/_includes/v24.3/cdc/core-csv.md @@ -1,3 +1,3 @@ {{site.data.alerts.callout_info}} -To determine how wide the columns need to be, the default `table` display format in `cockroach sql` buffers the results it receives from the server before printing them to the console. When consuming core changefeed data using `cockroach sql`, it's important to use a display format like `csv` that does not buffer its results. To set the display format, use the [`--format=csv` flag]({% link {{ page.version.version }}/cockroach-sql.md %}#sql-flag-format) when starting the [built-in SQL client]({% link {{ page.version.version }}/cockroach-sql.md %}), or set the [`\set display_format=csv` option]({% link {{ page.version.version }}/cockroach-sql.md %}#client-side-options) once the SQL client is open. +To determine how wide the columns need to be, the default `table` display format in `cockroach sql` buffers the results it receives from the server before printing them to the console. When consuming basic changefeed data using `cockroach sql`, it's important to use a display format like `csv` that does not buffer its results. To set the display format, use the [`--format=csv` flag]({% link {{ page.version.version }}/cockroach-sql.md %}#sql-flag-format) when starting the [built-in SQL client]({% link {{ page.version.version }}/cockroach-sql.md %}), or set the [`\set display_format=csv` option]({% link {{ page.version.version }}/cockroach-sql.md %}#client-side-options) once the SQL client is open. {{site.data.alerts.end}} diff --git a/src/current/_includes/v24.3/cdc/core-url.md b/src/current/_includes/v24.3/cdc/core-url.md index 35e530f8ae2..029e0ac40b7 100644 --- a/src/current/_includes/v24.3/cdc/core-url.md +++ b/src/current/_includes/v24.3/cdc/core-url.md @@ -1,3 +1,3 @@ {{site.data.alerts.callout_info}} -Because core changefeeds return results differently than other SQL statements, they require a dedicated database connection with specific settings around result buffering. In normal operation, CockroachDB improves performance by buffering results server-side before returning them to a client; however, result buffering is automatically turned off for core changefeeds. Core changefeeds also have different cancellation behavior than other queries: they can only be canceled by closing the underlying connection or issuing a [`CANCEL QUERY`]({% link {{ page.version.version }}/cancel-query.md %}) statement on a separate connection. Combined, these attributes of changefeeds mean that applications should explicitly create dedicated connections to consume changefeed data, instead of using a connection pool as most client drivers do by default. +Because basic changefeeds return results differently than other SQL statements, they require a dedicated database connection with specific settings around result buffering. In normal operation, CockroachDB improves performance by buffering results server-side before returning them to a client; however, result buffering is automatically turned off for basic changefeeds. basic changefeeds also have different cancellation behavior than other queries: they can only be canceled by closing the underlying connection or issuing a [`CANCEL QUERY`]({% link {{ page.version.version }}/cancel-query.md %}) statement on a separate connection. Combined, these attributes of changefeeds mean that applications should explicitly create dedicated connections to consume changefeed data, instead of using a connection pool as most client drivers do by default. {{site.data.alerts.end}} diff --git a/src/current/_includes/v24.3/cdc/create-core-changefeed-avro.md b/src/current/_includes/v24.3/cdc/create-core-changefeed-avro.md index 671b61c42f8..53dab65cff2 100644 --- a/src/current/_includes/v24.3/cdc/create-core-changefeed-avro.md +++ b/src/current/_includes/v24.3/cdc/create-core-changefeed-avro.md @@ -1,4 +1,4 @@ -In this example, you'll set up a core changefeed for a single-node cluster that emits Avro records. CockroachDB's Avro binary encoding convention uses the [Confluent Schema Registry](https://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html) to store Avro schemas. +In this example, you'll set up a basic changefeed for a single-node cluster that emits Avro records. CockroachDB's Avro binary encoding convention uses the [Confluent Schema Registry](https://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html) to store Avro schemas. 1. Use the [`cockroach start-single-node`]({% link {{ page.version.version }}/cockroach-start-single-node.md %}) command to start a single-node cluster: @@ -53,7 +53,7 @@ In this example, you'll set up a core changefeed for a single-node cluster that > INSERT INTO bar VALUES (0); ~~~ -1. Start the core changefeed: +1. Start the basic changefeed: {% include_cached copy-clipboard.html %} ~~~ sql @@ -72,13 +72,13 @@ In this example, you'll set up a core changefeed for a single-node cluster that $ cockroach sql --insecure -e "INSERT INTO bar VALUES (1)" ~~~ -1. Back in the terminal where the core changefeed is streaming, the output will appear: +1. Back in the terminal where the basic changefeed is streaming, the output will appear: ~~~ bar,\000\000\000\000\001\002\002,\000\000\000\000\002\002\002\002 ~~~ - Note that records may take a couple of seconds to display in the core changefeed. + Note that records may take a couple of seconds to display in the basic changefeed. 1. To stop streaming the changefeed, enter **CTRL+C** into the terminal where the changefeed is running. diff --git a/src/current/_includes/v24.3/cdc/create-core-changefeed.md b/src/current/_includes/v24.3/cdc/create-core-changefeed.md index ccb942bbdf4..df2264501a0 100644 --- a/src/current/_includes/v24.3/cdc/create-core-changefeed.md +++ b/src/current/_includes/v24.3/cdc/create-core-changefeed.md @@ -1,4 +1,4 @@ -In this example, you'll set up a core changefeed for a single-node cluster. +In this example, you'll set up a basic changefeed for a single-node cluster. 1. In a terminal window, start `cockroach`: @@ -44,7 +44,7 @@ In this example, you'll set up a core changefeed for a single-node cluster. > INSERT INTO foo VALUES (0); ~~~ -1. Start the core changefeed: +1. Start the basic changefeed: {% include_cached copy-clipboard.html %} ~~~ sql @@ -62,13 +62,13 @@ In this example, you'll set up a core changefeed for a single-node cluster. $ cockroach sql --insecure -e "INSERT INTO foo VALUES (1)" ~~~ -1. Back in the terminal where the core changefeed is streaming, the following output has appeared: +1. Back in the terminal where the basic changefeed is streaming, the following output has appeared: ~~~ foo,[1],"{""after"": {""a"": 1}}" ~~~ - Note that records may take a couple of seconds to display in the core changefeed. + Note that records may take a couple of seconds to display in the basic changefeed. 1. To stop streaming the changefeed, enter **CTRL+C** into the terminal where the changefeed is running. diff --git a/src/current/_includes/v24.3/userfile-examples/freetier-userfile-note.md b/src/current/_includes/v24.3/userfile-examples/freetier-userfile-note.md index 672dc7a0813..165fda37677 100644 --- a/src/current/_includes/v24.3/userfile-examples/freetier-userfile-note.md +++ b/src/current/_includes/v24.3/userfile-examples/freetier-userfile-note.md @@ -1,5 +1,5 @@ {{site.data.alerts.callout_info}} -It is possible to [backup]({% link {{ page.version.version }}/backup.md %}), [restore]({% link {{ page.version.version }}/restore.md %}), [import]({% link {{ page.version.version }}/import-into.md %}), and run [core changefeeds](changefeed-for.html) in [CockroachDB {{ site.data.products.serverless }}](../cockroachcloud/quickstart.html) that have upgraded to v21.1 or later. +It is possible to [backup]({% link {{ page.version.version }}/backup.md %}), [restore]({% link {{ page.version.version }}/restore.md %}), [import]({% link {{ page.version.version }}/import-into.md %}), and run [basic changefeeds](changefeed-for.html) in [CockroachDB {{ site.data.products.serverless }}](../cockroachcloud/quickstart.html) that have upgraded to v21.1 or later. [`userfile`]({% link {{ page.version.version }}/use-userfile-storage.md %}) storage is available in CockroachDB {{ site.data.products.serverless }} clusters for backups, restores, and imports. {{site.data.alerts.end}} diff --git a/src/current/v24.3/change-data-capture-overview.md b/src/current/v24.3/change-data-capture-overview.md index bc44c5b9681..d2be1c4079e 100644 --- a/src/current/v24.3/change-data-capture-overview.md +++ b/src/current/v24.3/change-data-capture-overview.md @@ -26,7 +26,7 @@ CockroachDB has two implementations of changefeeds: - + @@ -124,7 +124,7 @@ CockroachDB has two implementations of changefeeds: To get started with changefeeds in CockroachDB, refer to: -- [Create and Configure Changefeeds]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}): Learn about the fundamentals of using SQL statements to create and manage Enterprise and Core changefeeds. +- [Create and Configure Changefeeds]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}): Learn about the fundamentals of using SQL statements to create and manage Enterprise and basic changefeeds. - [Changefeed Sinks]({% link {{ page.version.version }}/changefeed-sinks.md %}): The downstream system to which the changefeed emits changes. Learn about the supported sinks and configuration capabilities. - [Changefeed Messages]({% link {{ page.version.version }}/changefeed-messages.md %}): The change events that emit from the changefeed to your sink. Learn about how messages are ordered at your sink and the options to configure and format messages. - [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}): Step-by-step examples for connecting to each changefeed sink. diff --git a/src/current/v24.3/changefeed-examples.md b/src/current/v24.3/changefeed-examples.md index 35a4528539c..ba3dedc7515 100644 --- a/src/current/v24.3/changefeed-examples.md +++ b/src/current/v24.3/changefeed-examples.md @@ -5,7 +5,7 @@ toc: true docs_area: stream_data --- -This page provides step-by-step examples for using Core and {{ site.data.products.enterprise }} changefeeds. Creating {{ site.data.products.enterprise }} changefeeds is available on CockroachDB {{ site.data.products.basic }}, {{ site.data.products.standard }}, {{ site.data.products.advanced }}, and with an [{{ site.data.products.enterprise }} license](enterprise-licensing.html) on CockroachDB {{ site.data.products.core }} clusters. Core changefeeds are available in all products. +This page provides step-by-step examples for using Core and {{ site.data.products.enterprise }} changefeeds. Creating {{ site.data.products.enterprise }} changefeeds is available on CockroachDB {{ site.data.products.basic }}, {{ site.data.products.standard }}, {{ site.data.products.advanced }}, and with an [{{ site.data.products.enterprise }} license](enterprise-licensing.html) on CockroachDB {{ site.data.products.core }} clusters. Basic changefeeds are available in all products. For a summary of Core and {{ site.data.products.enterprise }} changefeed features, refer to the [Change Data Capture Overview]({% link {{ page.version.version }}/change-data-capture-overview.md %}) page. @@ -26,7 +26,7 @@ Use the following filters to show usage examples for either **Enterprise** or **
- +
@@ -775,17 +775,17 @@ In this example, you'll set up a changefeed for a single-node cluster that is co
-Core changefeeds stream row-level changes to a client until the underlying SQL connection is closed. +Basic changefeeds stream row-level changes to a client until the underlying SQL connection is closed. -## Create a Core changefeed +## Create a basic changefeed {% include {{ page.version.version }}/cdc/create-core-changefeed.md %} -## Create a Core changefeed using Avro +## Create a basic changefeed using Avro {% include {{ page.version.version }}/cdc/create-core-changefeed-avro.md %} -For further information on Core changefeeds, see [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}). +For further information on basic changefeeds, see [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}).
diff --git a/src/current/v24.3/changefeed-for.md b/src/current/v24.3/changefeed-for.md index 3db74ac6e1d..00f155acaa4 100644 --- a/src/current/v24.3/changefeed-for.md +++ b/src/current/v24.3/changefeed-for.md @@ -5,7 +5,7 @@ toc: true docs_area: reference.sql --- -The `EXPERIMENTAL CHANGEFEED FOR` [statement]({% link {{ page.version.version }}/sql-statements.md %}) creates a new core changefeed, which streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. A core changefeed can watch one table or multiple tables in a comma-separated list. +The `EXPERIMENTAL CHANGEFEED FOR` [statement]({% link {{ page.version.version }}/sql-statements.md %}) creates a new basic changefeed, which streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. A basic changefeed can watch one table or multiple tables in a comma-separated list. For more information, see [Change Data Capture Overview]({% link {{ page.version.version }}/change-data-capture-overview.md %}). @@ -23,7 +23,7 @@ There is continued support for the [legacy privilege model](#legacy-privilege-mo To create a changefeed with `EXPERIMENTAL CHANGEFEED FOR`, a user must have the `SELECT` privilege on the changefeed's source tables. -You can [grant]({% link {{ page.version.version }}/grant.md %}#grant-privileges-on-specific-tables-in-a-database) a user the `SELECT` privilege to allow them to create core changefeeds on a specific table: +You can [grant]({% link {{ page.version.version }}/grant.md %}#grant-privileges-on-specific-tables-in-a-database) a user the `SELECT` privilege to allow them to create basic changefeeds on a specific table: {% include_cached copy-clipboard.html %} ~~~sql @@ -36,9 +36,9 @@ Changefeeds can only be created by superusers, i.e., [members of the `admin` rol ## Considerations -- Because core changefeeds return results differently than other SQL statements, they require a dedicated database connection with specific settings around result buffering. In normal operation, CockroachDB improves performance by buffering results server-side before returning them to a client; however, result buffering is automatically turned off for core changefeeds. Core changefeeds also have different cancellation behavior than other queries: they can only be canceled by closing the underlying connection or issuing a [`CANCEL QUERY`]({% link {{ page.version.version }}/cancel-query.md %}) statement on a separate connection. Combined, these attributes of changefeeds mean that applications should explicitly create dedicated connections to consume changefeed data, instead of using a connection pool as most client drivers do by default. +- Because basic changefeeds return results differently than other SQL statements, they require a dedicated database connection with specific settings around result buffering. In normal operation, CockroachDB improves performance by buffering results server-side before returning them to a client; however, result buffering is automatically turned off for basic changefeeds. basic changefeeds also have different cancellation behavior than other queries: they can only be canceled by closing the underlying connection or issuing a [`CANCEL QUERY`]({% link {{ page.version.version }}/cancel-query.md %}) statement on a separate connection. Combined, these attributes of changefeeds mean that applications should explicitly create dedicated connections to consume changefeed data, instead of using a connection pool as most client drivers do by default. - This cancellation behavior (i.e., close the underlying connection to cancel the changefeed) also extends to client driver usage; in particular, when a client driver calls `Rows.Close()` after encountering errors for a stream of rows. The pgwire protocol requires that the rows be consumed before the connection is again usable, but in the case of a core changefeed, the rows are never consumed. It is therefore critical that you close the connection, otherwise the application will be blocked forever on `Rows.Close()`. + This cancellation behavior (i.e., close the underlying connection to cancel the changefeed) also extends to client driver usage; in particular, when a client driver calls `Rows.Close()` after encountering errors for a stream of rows. The pgwire protocol requires that the rows be consumed before the connection is again usable, but in the case of a basic changefeed, the rows are never consumed. It is therefore critical that you close the connection, otherwise the application will be blocked forever on `Rows.Close()`. - In most cases, each version of a row will be emitted once. However, some infrequent conditions (e.g., node failures, network partitions) will cause them to be repeated. This gives our changefeeds an at-least-once delivery guarantee. For more information, see [Ordering Guarantees]({% link {{ page.version.version }}/changefeed-messages.md %}#ordering-and-delivery-guarantees). - As of v22.1, changefeeds filter out [`VIRTUAL` computed columns]({% link {{ page.version.version }}/computed-columns.md %}) from events by default. This is a [backward-incompatible change]({% link releases/v22.1.md %}#v22-1-0-backward-incompatible-changes). To maintain the changefeed behavior in previous versions where [`NULL`]({% link {{ page.version.version }}/null-handling.md %}) values are emitted for virtual computed columns, see the [`virtual_columns`]({% link {{ page.version.version }}/changefeed-for.md %}#virtual-columns) option for more detail. @@ -95,14 +95,14 @@ To start a changefeed: EXPERIMENTAL CHANGEFEED FOR cdc_test; ~~~ -In the terminal where the core changefeed is streaming, the output will appear: +In the terminal where the basic changefeed is streaming, the output will appear: ~~~ table,key,value cdc_test,[0],"{""after"": {""a"": 0}}" ~~~ -For step-by-step guidance on creating a Core changefeed, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. +For step-by-step guidance on creating a basic changefeed, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. ### Create a changefeed with Avro @@ -113,14 +113,14 @@ To start a changefeed in Avro format: EXPERIMENTAL CHANGEFEED FOR cdc_test WITH format = avro, confluent_schema_registry = 'http://localhost:8081'; ~~~ -In the terminal where the core changefeed is streaming, the output will appear: +In the terminal where the basic changefeed is streaming, the output will appear: ~~~ table,key,value cdc_test,\000\000\000\000\001\002\000,\000\000\000\000\002\002\002\000 ~~~ -For step-by-step guidance on creating a Core changefeed with Avro, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. +For step-by-step guidance on creating a basic changefeed with Avro, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. ### Create a changefeed on a table with column families @@ -138,7 +138,7 @@ To create a changefeed on a table and output changes for each column family, use EXPERIMENTAL CHANGEFEED FOR TABLE cdc_test WITH split_column_families; ~~~ -For step-by-step guidance creating a Core changefeed on a table with multiple column families, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. +For step-by-step guidance creating a basic changefeed on a table with multiple column families, see the [Changefeed Examples]({% link {{ page.version.version }}/changefeed-examples.md %}) page. ## See also diff --git a/src/current/v24.3/changefeeds-on-tables-with-column-families.md b/src/current/v24.3/changefeeds-on-tables-with-column-families.md index 069242510ae..4a48b5c7f7d 100644 --- a/src/current/v24.3/changefeeds-on-tables-with-column-families.md +++ b/src/current/v24.3/changefeeds-on-tables-with-column-families.md @@ -28,7 +28,7 @@ CREATE CHANGEFEED FOR TABLE {table} FAMILY {family} INTO {sink}; ~~~ {{site.data.alerts.callout_info}} -You can also use [Core changefeeds]({% link {{ page.version.version }}/changefeeds-on-tables-with-column-families.md %}?filters=core#create-a-core-changefeed-on-a-table-with-column-families) on tables with column families by using the [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}) statement with `split_column_families` or the `FAMILY` keyword. +You can also use [basic changefeeds]({% link {{ page.version.version }}/changefeeds-on-tables-with-column-families.md %}?filters=core#create-a-basic-changefeed-on-a-table-with-column-families) on tables with column families by using the [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}) statement with `split_column_families` or the `FAMILY` keyword. {{site.data.alerts.end}} If a table has multiple column families, the `FAMILY` keyword will ensure the changefeed emits messages for **each** column family you define with `FAMILY` in the `CREATE CHANGEFEED` statement. If you do not specify `FAMILY`, then the changefeed will emit messages for **all** the table's column families. @@ -83,11 +83,11 @@ The output shows the `primary` column family with `4` in the value (`{"id":4,"na - Creating a changefeed with [CDC queries]({% link {{ page.version.version }}/cdc-queries.md %}) is not supported on tables with more than one column family. - When you create a changefeed on a table with more than one column family, the changefeed will emit messages per column family in separate streams. As a result, [changefeed messages]({% link {{ page.version.version }}/changefeed-messages.md %}) for different column families will arrive at the [sink]({% link {{ page.version.version }}/changefeed-sinks.md %}) under separate topics. For more details, refer to [Message format](#message-format). -For examples of starting changefeeds on tables with column families, see the following examples for Enterprise and Core changefeeds. +For examples of starting changefeeds on tables with column families, see the following examples for Enterprise and basic changefeeds.
- +
@@ -301,9 +301,9 @@ In this example, you'll set up changefeeds on two tables that have [column famil
-## Create a Core changefeed on a table with column families +## Create a basic changefeed on a table with column families -In this example, you'll set up Core changefeeds on two tables that have [column families]({% link {{ page.version.version }}/column-families.md %}). You'll use a single-node cluster with the Core changefeed sending changes to the client. +In this example, you'll set up basic changefeeds on two tables that have [column families]({% link {{ page.version.version }}/column-families.md %}). You'll use a single-node cluster with the basic changefeed sending changes to the client. 1. Use the [`cockroach start-single-node`]({% link {{ page.version.version }}/cockroach-start-single-node.md %}) command to start a single-node cluster: diff --git a/src/current/v24.3/cockroachdb-feature-availability.md b/src/current/v24.3/cockroachdb-feature-availability.md index 65893f62586..1116b63b0e7 100644 --- a/src/current/v24.3/cockroachdb-feature-availability.md +++ b/src/current/v24.3/cockroachdb-feature-availability.md @@ -238,7 +238,7 @@ For an Apache Pulsar setup example, refer to the [Changefeed Examples]({% link { ### Core implementation of changefeeds -The [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}) statement creates a new core changefeed, which streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. A core changefeed can watch one table or multiple tables in a comma-separated list. +The [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.version.version }}/changefeed-for.md %}) statement creates a new basic changefeed, which streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. A basic changefeed can watch one table or multiple tables in a comma-separated list. ### Multiple active portals diff --git a/src/current/v24.3/create-and-configure-changefeeds.md b/src/current/v24.3/create-and-configure-changefeeds.md index 17f5686dedc..b3f95c62602 100644 --- a/src/current/v24.3/create-and-configure-changefeeds.md +++ b/src/current/v24.3/create-and-configure-changefeeds.md @@ -15,7 +15,7 @@ This page describes: ## Before you create a changefeed 1. Enable rangefeeds on CockroachDB {{ site.data.products.dedicated }} and CockroachDB {{ site.data.products.core }}. Refer to [Enable rangefeeds](#enable-rangefeeds) for instructions. -1. Decide on whether you will run an {{ site.data.products.enterprise }} or Core changefeed. Refer to the [Overview]({% link {{ page.version.version }}/change-data-capture-overview.md %}) page for a comparative capability table. +1. Decide on whether you will run an {{ site.data.products.enterprise }} or basic changefeed. Refer to the [Overview]({% link {{ page.version.version }}/change-data-capture-overview.md %}) page for a comparative capability table. 1. Plan the number of changefeeds versus the number of tables to include in a single changefeed for your cluster. {% include {{ page.version.version }}/cdc/changefeed-number-limit.md %} Refer to [System resources and running changefeeds](#system-resources-and-running-changefeeds) and [Recommendations for the number of target tables](#recommendations-for-the-number-of-target-tables). 1. Consider whether your {{ site.data.products.enterprise }} [changefeed use case](#create) would be better served by [change data capture queries]({% link {{ page.version.version }}/cdc-queries.md %}) that can filter data on a single table. CDC queries can improve the efficiency of changefeeds because the job will not need to encode as much change data. 1. Read the [Considerations](#considerations) section that provides information on changefeed interactions that could affect how you configure or run your changefeed. @@ -78,7 +78,7 @@ The following Enterprise and Core sections outline how to create and configure e
- +
@@ -170,9 +170,9 @@ For more information, refer to [`CANCEL JOB`]({% link {{ page.version.version }} ## Create a changefeed -A core changefeed streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. +A basic changefeed streams row-level changes to the client indefinitely until the underlying connection is closed or the changefeed is canceled. -To create a core changefeed: +To create a basic changefeed: {% include_cached copy-clipboard.html %} ~~~ sql diff --git a/src/current/v24.3/create-changefeed.md b/src/current/v24.3/create-changefeed.md index ea240456986..2b9068356dc 100644 --- a/src/current/v24.3/create-changefeed.md +++ b/src/current/v24.3/create-changefeed.md @@ -36,7 +36,7 @@ To create a changefeed, the user must be a member of the `admin` role or have th Parameter | Description ----------|------------ `table_name` | The name of the table (or tables in a comma separated list) to create a changefeed for.

**Note:** Before creating a changefeed, consider the number of changefeeds versus the number of tables to include in a single changefeed. Each scenario can have an impact on total memory usage or changefeed performance. Refer to [Create and Configure Changefeeds]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}) for more detail. -`sink` | The location of the configurable sink. The scheme of the URI indicates the type. For more information, refer to [Sink URI](#sink-uri).

**Note:** If you create a changefeed without a sink, your changefeed will run like a [core changefeed]({% link {{ page.version.version }}/changefeed-for.md %}) sending messages to the SQL client. For more detail, refer to the [Create and Configure Changefeeds]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}#create) page. +`sink` | The location of the configurable sink. The scheme of the URI indicates the type. For more information, refer to [Sink URI](#sink-uri).

**Note:** If you create a changefeed without a sink, your changefeed will run like a [basic changefeed]({% link {{ page.version.version }}/changefeed-for.md %}) sending messages to the SQL client. For more detail, refer to the [Create and Configure Changefeeds]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}#create) page. `option` / `value` | For a list of available options and their values, refer to [Options](#options). ### CDC query parameters diff --git a/src/current/v24.3/licensing-faqs.md b/src/current/v24.3/licensing-faqs.md index 4971b930de0..7ae59362193 100644 --- a/src/current/v24.3/licensing-faqs.md +++ b/src/current/v24.3/licensing-faqs.md @@ -53,7 +53,7 @@ Feature | BSL | CCL (free) | CCL (paid) **[Full backups]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#full-backups)** | | ✓ | **[Incremental backups]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups)** | | | ✓ **[Other advanced backup features]({% link {{ page.version.version }}/backup.md %})** | | | ✓ -**[Core changefeed](create-and-configure-changefeeds.html?filters=core)** | | ✓ | +**[basic changefeed](create-and-configure-changefeeds.html?filters=core)** | | ✓ | **[{{ site.data.products.enterprise }} changefeed]({% link {{ page.version.version }}/create-and-configure-changefeeds.md %}#configure-a-changefeed)** | | | ✓ **[Table-level zone configuration]({% link {{ page.version.version }}/configure-replication-zones.md %}#replication-zone-levels)** | ✓ | | **[Multi-region capabilities]({% link {{ page.version.version }}/multiregion-overview.md %})** | | | ✓
Core changefeedsBasic changefeeds Enterprise changefeeds