Streaming

rpk registry compatibility-level set

Set the global or per-subject compatibility levels.

Running this command without a subject sets the global compatibility level. To set the global level at the same time as per-subject levels, use the --global flag.

LEVELS:

  • BACKWARD (default): Consumers using the new schema (for example, version 10) can read data from producers using the previous schema (for example, version 9).

  • BACKWARD_TRANSITIVE: Consumers using the new schema (for example, version . can read data from producers using all previous schemas (for example, versions 1-9).

  • FORWARD: Consumers using the previous schema (for example, version 9) can read data from producers using the new schema (for example, version 10).

  • FORWARD_TRANSITIVE: Consumers using any previous schema (for example, versions 1-9) can read data from producers using the new schema (for example, version 10).

  • FULL: A new schema and the previous schema (for example, versions 10 and 9) are both backward and forward compatible with each other.

  • FULL_TRANSITIVE: Each schema is both backward and forward compatible with all registered schemas.

  • NONE: No schema compatibility checks are done.

Usage

rpk registry compatibility-level set <subject...> [flags]

Flags

Value Type Description

--global

bool

Set the global level in addition to subject levels.

--level

string

Level to set, see the help text of this command for the full list.

Global flags

Value Type Description

--config

string

Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml.

-X, --config-opt

stringArray

Override rpk configuration settings; -X help for detail or -X list for terser detail.

--ignore-profile

bool

Ignore rpk.yaml and redpanda.yaml; use default settings.

--profile

string

rpk profile to use.

-v, --verbose

bool

Enable verbose logging.