Skip to content

Commit c919565

Browse files
committed
add more props
1 parent 3ceb3e0 commit c919565

1 file changed

Lines changed: 161 additions & 1 deletion

File tree

modules/reference/pages/properties/topic-properties.adoc

Lines changed: 161 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -594,6 +594,24 @@ A flag for enabling Redpanda to upload data for a topic from local storage to ob
594594

595595
- xref:manage:tiered-storage.adoc[Tiered Storage]
596596

597+
---
598+
[[redpandaremoteallowgaps]]
599+
=== redpanda.remote.allowgaps
600+
601+
Controls the eviction of locally stored log segments when Tiered Storage uploads are paused for this topic. Set to `false` (default) to only evict data that has already been uploaded to object storage. If the retained data fills the local volume, Redpanda throttles producers. Set to `true` to allow the eviction of locally stored log segments, which may create gaps in offsets.
602+
603+
This topic-level property overrides the cluster-level xref:./cluster-properties.adoc#cloud_storage_enable_remote_allow_gaps[`cloud_storage_enable_remote_allow_gaps`] property for the topic.
604+
605+
*Type:* boolean
606+
607+
*Default:* `false`
608+
609+
*Related cluster property:* xref:./cluster-properties.adoc#cloud_storage_enable_remote_allow_gaps[`cloud_storage_enable_remote_allow_gaps`]
610+
611+
**Related topics**:
612+
613+
- xref:manage:tiered-storage.adoc[Tiered Storage]
614+
597615
---
598616
[[retentionlocaltargetbytes]]
599617
=== retention.local.target.bytes
@@ -739,4 +757,146 @@ Controls how often the data in the Iceberg table is refreshed with new data from
739757

740758
**Related topics**:
741759

742-
- xref:manage:iceberg/about-iceberg-topics.adoc[]
760+
- xref:manage:iceberg/about-iceberg-topics.adoc[]
761+
762+
---
763+
== Schema Registry and Validation Properties
764+
765+
These properties control server-side schema ID validation for topics when using Schema Registry.
766+
767+
[[redpandakeyschemavalidation]]
768+
=== redpanda.key.schema.id.validation
769+
770+
Enable validation of the schema ID for keys on a record. When enabled, Redpanda validates that the schema ID encoded in the record's key is registered in the Schema Registry according to the configured subject name strategy.
771+
772+
*Type:* boolean
773+
774+
*Default:* `false`
775+
776+
**Related topics**:
777+
778+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
779+
780+
---
781+
[[redpandakeysubjectnamestrategy]]
782+
=== redpanda.key.subject.name.strategy
783+
784+
The subject name strategy for keys when `redpanda.key.schema.id.validation` is enabled. This determines how the topic and schema are mapped to a subject name in the Schema Registry.
785+
786+
*Type:* string
787+
788+
*Default:* `TopicNameStrategy`
789+
790+
*Accepted values:* [`TopicNameStrategy`, `RecordNameStrategy`, `TopicRecordNameStrategy`]
791+
792+
**Related topics**:
793+
794+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
795+
796+
---
797+
[[redpandavalueschemavalidation]]
798+
=== redpanda.value.schema.id.validation
799+
800+
Enable validation of the schema ID for values on a record. When enabled, Redpanda validates that the schema ID encoded in the record's value is registered in the Schema Registry according to the configured subject name strategy.
801+
802+
*Type:* boolean
803+
804+
*Default:* `false`
805+
806+
**Related topics**:
807+
808+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
809+
810+
---
811+
[[redpandavaluesubjectnamestrategy]]
812+
=== redpanda.value.subject.name.strategy
813+
814+
The subject name strategy for values when `redpanda.value.schema.id.validation` is enabled. This determines how the topic and schema are mapped to a subject name in the Schema Registry.
815+
816+
*Type:* string
817+
818+
*Default:* `TopicNameStrategy`
819+
820+
*Accepted values:* [`TopicNameStrategy`, `RecordNameStrategy`, `TopicRecordNameStrategy`]
821+
822+
**Related topics**:
823+
824+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
825+
826+
---
827+
[[confluentkeyschemavalidation]]
828+
=== confluent.key.schema.validation
829+
830+
Enable validation of the schema ID for keys on a record. This is a compatibility alias for `redpanda.key.schema.id.validation`. When enabled, Redpanda validates that the schema ID encoded in the record's key is registered in the Schema Registry according to the configured subject name strategy.
831+
832+
*Type:* boolean
833+
834+
*Default:* `false`
835+
836+
**Related topics**:
837+
838+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
839+
840+
---
841+
[[confluentkeysubjectnamestrategy]]
842+
=== confluent.key.subject.name.strategy
843+
844+
The subject name strategy for keys when `confluent.key.schema.validation` is enabled. This is a compatibility alias for `redpanda.key.subject.name.strategy`. This determines how the topic and schema are mapped to a subject name in the Schema Registry.
845+
846+
*Type:* string
847+
848+
*Default:* `io.confluent.kafka.serializers.subject.TopicNameStrategy`
849+
850+
*Accepted values:* [`io.confluent.kafka.serializers.subject.TopicNameStrategy`, `io.confluent.kafka.serializers.subject.RecordNameStrategy`, `io.confluent.kafka.serializers.subject.TopicRecordNameStrategy`]
851+
852+
**Related topics**:
853+
854+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
855+
856+
---
857+
[[confluentvalueschemavalidation]]
858+
=== confluent.value.schema.validation
859+
860+
Enable validation of the schema ID for values on a record. This is a compatibility alias for `redpanda.value.schema.id.validation`. When enabled, Redpanda validates that the schema ID encoded in the record's value is registered in the Schema Registry according to the configured subject name strategy.
861+
862+
*Type:* boolean
863+
864+
*Default:* `false`
865+
866+
**Related topics**:
867+
868+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
869+
870+
---
871+
[[confluentvaluesubjectnamestrategy]]
872+
=== confluent.value.subject.name.strategy
873+
874+
The subject name strategy for values when `confluent.value.schema.validation` is enabled. This is a compatibility alias for `redpanda.value.subject.name.strategy`. This determines how the topic and schema are mapped to a subject name in the Schema Registry.
875+
876+
*Type:* string
877+
878+
*Default:* `io.confluent.kafka.serializers.subject.TopicNameStrategy`
879+
880+
*Accepted values:* [`io.confluent.kafka.serializers.subject.TopicNameStrategy`, `io.confluent.kafka.serializers.subject.RecordNameStrategy`, `io.confluent.kafka.serializers.subject.TopicRecordNameStrategy`]
881+
882+
**Related topics**:
883+
884+
- xref:manage:schema-reg/schema-id-validation.adoc[Server-Side Schema ID Validation]
885+
886+
---
887+
== Virtual Cluster and Cloud Topic Properties
888+
889+
These properties are used for advanced features like virtual clustering and cloud topics.
890+
891+
[[redpandavirtualclusterid]]
892+
=== redpanda.virtual.cluster.id
893+
894+
The virtual cluster ID for this topic. This property is used for multiplexing topics across virtual clusters within a single physical cluster. This property can only be set when creating a topic and requires the `enable_mpx_extensions` cluster property to be enabled.
895+
896+
*Type:* string
897+
898+
*Default:* null
899+
900+
**Related topics**:
901+
902+
- Virtual cluster functionality (requires enabling multiplexing extensions)

0 commit comments

Comments
 (0)