Aiven v6.44.0 published on Friday, Oct 10, 2025 by Pulumi
aiven.getKafkaTopic
Gets information about an Aiven for Apache Kafka® topic.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as aiven from "@pulumi/aiven";
const exampleTopic = aiven.getKafkaTopic({
    project: exampleProject.project,
    serviceName: exampleKafka.serviceName,
    topicName: "example-topic",
});
import pulumi
import pulumi_aiven as aiven
example_topic = aiven.get_kafka_topic(project=example_project["project"],
    service_name=example_kafka["serviceName"],
    topic_name="example-topic")
package main
import (
	"github.com/pulumi/pulumi-aiven/sdk/v6/go/aiven"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := aiven.LookupKafkaTopic(ctx, &aiven.LookupKafkaTopicArgs{
			Project:     exampleProject.Project,
			ServiceName: exampleKafka.ServiceName,
			TopicName:   "example-topic",
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aiven = Pulumi.Aiven;
return await Deployment.RunAsync(() => 
{
    var exampleTopic = Aiven.GetKafkaTopic.Invoke(new()
    {
        Project = exampleProject.Project,
        ServiceName = exampleKafka.ServiceName,
        TopicName = "example-topic",
    });
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aiven.AivenFunctions;
import com.pulumi.aiven.inputs.GetKafkaTopicArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }
    public static void stack(Context ctx) {
        final var exampleTopic = AivenFunctions.getKafkaTopic(GetKafkaTopicArgs.builder()
            .project(exampleProject.project())
            .serviceName(exampleKafka.serviceName())
            .topicName("example-topic")
            .build());
    }
}
variables:
  exampleTopic:
    fn::invoke:
      function: aiven:getKafkaTopic
      arguments:
        project: ${exampleProject.project}
        serviceName: ${exampleKafka.serviceName}
        topicName: example-topic
Using getKafkaTopic
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getKafkaTopic(args: GetKafkaTopicArgs, opts?: InvokeOptions): Promise<GetKafkaTopicResult>
function getKafkaTopicOutput(args: GetKafkaTopicOutputArgs, opts?: InvokeOptions): Output<GetKafkaTopicResult>def get_kafka_topic(project: Optional[str] = None,
                    service_name: Optional[str] = None,
                    topic_name: Optional[str] = None,
                    opts: Optional[InvokeOptions] = None) -> GetKafkaTopicResult
def get_kafka_topic_output(project: Optional[pulumi.Input[str]] = None,
                    service_name: Optional[pulumi.Input[str]] = None,
                    topic_name: Optional[pulumi.Input[str]] = None,
                    opts: Optional[InvokeOptions] = None) -> Output[GetKafkaTopicResult]func LookupKafkaTopic(ctx *Context, args *LookupKafkaTopicArgs, opts ...InvokeOption) (*LookupKafkaTopicResult, error)
func LookupKafkaTopicOutput(ctx *Context, args *LookupKafkaTopicOutputArgs, opts ...InvokeOption) LookupKafkaTopicResultOutput> Note: This function is named LookupKafkaTopic in the Go SDK.
public static class GetKafkaTopic 
{
    public static Task<GetKafkaTopicResult> InvokeAsync(GetKafkaTopicArgs args, InvokeOptions? opts = null)
    public static Output<GetKafkaTopicResult> Invoke(GetKafkaTopicInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetKafkaTopicResult> getKafkaTopic(GetKafkaTopicArgs args, InvokeOptions options)
public static Output<GetKafkaTopicResult> getKafkaTopic(GetKafkaTopicArgs args, InvokeOptions options)
fn::invoke:
  function: aiven:index/getKafkaTopic:getKafkaTopic
  arguments:
    # arguments dictionaryThe following arguments are supported:
- Project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- ServiceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- TopicName string
- The name of the topic. Changing this property forces recreation of the resource.
- Project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- ServiceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- TopicName string
- The name of the topic. Changing this property forces recreation of the resource.
- project String
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- serviceName String
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- topicName String
- The name of the topic. Changing this property forces recreation of the resource.
- project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- serviceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- topicName string
- The name of the topic. Changing this property forces recreation of the resource.
- project str
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- service_name str
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- topic_name str
- The name of the topic. Changing this property forces recreation of the resource.
- project String
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- serviceName String
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- topicName String
- The name of the topic. Changing this property forces recreation of the resource.
getKafkaTopic Result
The following output properties are available:
- Configs
List<GetKafka Topic Config> 
- Advanced parameters to configure topics.
- Id string
- The provider-assigned unique ID for this managed resource.
- OwnerUser stringGroup Id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- Partitions int
- The number of partitions to create in the topic.
- Project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- Replication int
- The replication factor for the topic.
- ServiceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- 
List<GetKafka Topic Tag> 
- Tags for the topic.
- TerminationProtection bool
- TopicDescription string
- The description of the topic
- TopicName string
- The name of the topic. Changing this property forces recreation of the resource.
- Configs
[]GetKafka Topic Config 
- Advanced parameters to configure topics.
- Id string
- The provider-assigned unique ID for this managed resource.
- OwnerUser stringGroup Id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- Partitions int
- The number of partitions to create in the topic.
- Project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- Replication int
- The replication factor for the topic.
- ServiceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- 
[]GetKafka Topic Tag 
- Tags for the topic.
- TerminationProtection bool
- TopicDescription string
- The description of the topic
- TopicName string
- The name of the topic. Changing this property forces recreation of the resource.
- configs
List<GetKafka Topic Config> 
- Advanced parameters to configure topics.
- id String
- The provider-assigned unique ID for this managed resource.
- ownerUser StringGroup Id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- partitions Integer
- The number of partitions to create in the topic.
- project String
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- replication Integer
- The replication factor for the topic.
- serviceName String
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- 
List<GetKafka Topic Tag> 
- Tags for the topic.
- terminationProtection Boolean
- topicDescription String
- The description of the topic
- topicName String
- The name of the topic. Changing this property forces recreation of the resource.
- configs
GetKafka Topic Config[] 
- Advanced parameters to configure topics.
- id string
- The provider-assigned unique ID for this managed resource.
- ownerUser stringGroup Id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- partitions number
- The number of partitions to create in the topic.
- project string
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- replication number
- The replication factor for the topic.
- serviceName string
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- 
GetKafka Topic Tag[] 
- Tags for the topic.
- terminationProtection boolean
- topicDescription string
- The description of the topic
- topicName string
- The name of the topic. Changing this property forces recreation of the resource.
- configs
Sequence[GetKafka Topic Config] 
- Advanced parameters to configure topics.
- id str
- The provider-assigned unique ID for this managed resource.
- owner_user_ strgroup_ id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- partitions int
- The number of partitions to create in the topic.
- project str
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- replication int
- The replication factor for the topic.
- service_name str
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- 
Sequence[GetKafka Topic Tag] 
- Tags for the topic.
- termination_protection bool
- topic_description str
- The description of the topic
- topic_name str
- The name of the topic. Changing this property forces recreation of the resource.
- configs List<Property Map>
- Advanced parameters to configure topics.
- id String
- The provider-assigned unique ID for this managed resource.
- ownerUser StringGroup Id 
- The ID of the user group that owns the topic. Assigning ownership to decentralize topic management is part of Aiven for Apache Kafka® governance.
- partitions Number
- The number of partitions to create in the topic.
- project String
- The name of the project this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- replication Number
- The replication factor for the topic.
- serviceName String
- The name of the service that this resource belongs to. To set up proper dependencies please refer to this variable as a reference. Changing this property forces recreation of the resource.
- List<Property Map>
- Tags for the topic.
- terminationProtection Boolean
- topicDescription String
- The description of the topic
- topicName String
- The name of the topic. Changing this property forces recreation of the resource.
Supporting Types
GetKafkaTopicConfig   
- CleanupPolicy string
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- CompressionType string
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- DeleteRetention stringMs 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- DisklessEnable bool
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- FileDelete stringDelay Ms 
- The time to wait before deleting a file from the filesystem.
- FlushMessages string
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- FlushMs string
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- IndexInterval stringBytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- LocalRetention stringBytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- LocalRetention stringMs 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- MaxCompaction stringLag Ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- MaxMessage stringBytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- MessageDownconversion boolEnable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- MessageFormat stringVersion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- MessageTimestamp stringDifference Max Ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- MessageTimestamp stringType 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- MinCleanable doubleDirty Ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- MinCompaction stringLag Ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- MinInsync stringReplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- Preallocate bool
- True if we should preallocate the file on disk when creating a new log segment.
- RemoteStorage boolEnable 
- Indicates whether tiered storage should be enabled.
- RetentionBytes string
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- RetentionMs string
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- SegmentBytes string
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- SegmentIndex stringBytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- SegmentJitter stringMs 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- SegmentMs string
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- UncleanLeader boolElection Enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
- CleanupPolicy string
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- CompressionType string
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- DeleteRetention stringMs 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- DisklessEnable bool
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- FileDelete stringDelay Ms 
- The time to wait before deleting a file from the filesystem.
- FlushMessages string
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- FlushMs string
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- IndexInterval stringBytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- LocalRetention stringBytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- LocalRetention stringMs 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- MaxCompaction stringLag Ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- MaxMessage stringBytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- MessageDownconversion boolEnable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- MessageFormat stringVersion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- MessageTimestamp stringDifference Max Ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- MessageTimestamp stringType 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- MinCleanable float64Dirty Ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- MinCompaction stringLag Ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- MinInsync stringReplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- Preallocate bool
- True if we should preallocate the file on disk when creating a new log segment.
- RemoteStorage boolEnable 
- Indicates whether tiered storage should be enabled.
- RetentionBytes string
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- RetentionMs string
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- SegmentBytes string
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- SegmentIndex stringBytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- SegmentJitter stringMs 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- SegmentMs string
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- UncleanLeader boolElection Enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
- cleanupPolicy String
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- compressionType String
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- deleteRetention StringMs 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- disklessEnable Boolean
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- fileDelete StringDelay Ms 
- The time to wait before deleting a file from the filesystem.
- flushMessages String
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- flushMs String
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- indexInterval StringBytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- localRetention StringBytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- localRetention StringMs 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- maxCompaction StringLag Ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- maxMessage StringBytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- messageDownconversion BooleanEnable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- messageFormat StringVersion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- messageTimestamp StringDifference Max Ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- messageTimestamp StringType 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- minCleanable DoubleDirty Ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- minCompaction StringLag Ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- minInsync StringReplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- preallocate Boolean
- True if we should preallocate the file on disk when creating a new log segment.
- remoteStorage BooleanEnable 
- Indicates whether tiered storage should be enabled.
- retentionBytes String
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- retentionMs String
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- segmentBytes String
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentIndex StringBytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentJitter StringMs 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- segmentMs String
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- uncleanLeader BooleanElection Enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
- cleanupPolicy string
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- compressionType string
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- deleteRetention stringMs 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- disklessEnable boolean
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- fileDelete stringDelay Ms 
- The time to wait before deleting a file from the filesystem.
- flushMessages string
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- flushMs string
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- indexInterval stringBytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- localRetention stringBytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- localRetention stringMs 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- maxCompaction stringLag Ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- maxMessage stringBytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- messageDownconversion booleanEnable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- messageFormat stringVersion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- messageTimestamp stringDifference Max Ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- messageTimestamp stringType 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- minCleanable numberDirty Ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- minCompaction stringLag Ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- minInsync stringReplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- preallocate boolean
- True if we should preallocate the file on disk when creating a new log segment.
- remoteStorage booleanEnable 
- Indicates whether tiered storage should be enabled.
- retentionBytes string
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- retentionMs string
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- segmentBytes string
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentIndex stringBytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentJitter stringMs 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- segmentMs string
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- uncleanLeader booleanElection Enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
- cleanup_policy str
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- compression_type str
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- delete_retention_ strms 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- diskless_enable bool
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- file_delete_ strdelay_ ms 
- The time to wait before deleting a file from the filesystem.
- flush_messages str
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- flush_ms str
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- index_interval_ strbytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- local_retention_ strbytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- local_retention_ strms 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- max_compaction_ strlag_ ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- max_message_ strbytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- message_downconversion_ boolenable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- message_format_ strversion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- message_timestamp_ strdifference_ max_ ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- message_timestamp_ strtype 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- min_cleanable_ floatdirty_ ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- min_compaction_ strlag_ ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- min_insync_ strreplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- preallocate bool
- True if we should preallocate the file on disk when creating a new log segment.
- remote_storage_ boolenable 
- Indicates whether tiered storage should be enabled.
- retention_bytes str
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- retention_ms str
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- segment_bytes str
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segment_index_ strbytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segment_jitter_ strms 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- segment_ms str
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- unclean_leader_ boolelection_ enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
- cleanupPolicy String
- The retention policy to use on old segments. Possible values include 'delete', 'compact', or a comma-separated list of them. The default policy ('delete') will discard old segments when their retention time or size limit has been reached. The 'compact' setting will enable log compaction on the topic. The possible values are compact,compact,deleteanddelete.
- compressionType String
- Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer. The possible values are gzip,lz4,producer,snappy,uncompressedandzstd.
- deleteRetention StringMs 
- The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise delete tombstones may be collected before they complete their scan).
- disklessEnable Boolean
- Creates a diskless topic. You can only do this when you create the topic and you cannot change it later. Diskless topics are only available for bring your own cloud (BYOC) services that have the feature enabled.
- fileDelete StringDelay Ms 
- The time to wait before deleting a file from the filesystem.
- flushMessages String
- This setting allows specifying an interval at which we will force an fsync of data written to the log. For example if this was set to 1 we would fsync after every message; if it were 5 we would fsync after every five messages. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- flushMs String
- This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.
- indexInterval StringBytes 
- This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.
- localRetention StringBytes 
- This configuration controls the maximum bytes tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the limit is equal to overall retention time. If set to -1, no limit is applied but it's possible only if overall retention is also -1.
- localRetention StringMs 
- This configuration controls the maximum time tiered storage will retain segment files locally before it will discard old log segments to free up space. If set to -2, the time limit is equal to overall retention time. If set to -1, no time limit is applied but it's possible only if overall retention is also -1.
- maxCompaction StringLag Ms 
- The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.
- maxMessage StringBytes 
- The largest record batch size allowed by Kafka (after compression if compression is enabled). If this is increased and there are consumers older than 0.10.2, the consumers' fetch size must also be increased so that the they can fetch record batches this large. In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.
- messageDownconversion BooleanEnable 
- This configuration controls whether down-conversion of message formats is enabled to satisfy consume requests. When set to false, broker will not perform down-conversion for consumers expecting an older message format. The broker responds with UNSUPPORTED_VERSION error for consume requests from such older clients. This configuration does not apply to any message format conversion that might be required for replication to followers.
- messageFormat StringVersion 
- Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don't understand. Deprecated in Kafka 4.0+: this configuration is removed and any supplied value will be ignored; for services upgraded to 4.0+, the returned value may be 'None'. The possible values are 0.10.0,0.10.0-IV0,0.10.0-IV1,0.10.1,0.10.1-IV0,0.10.1-IV1,0.10.1-IV2,0.10.2,0.10.2-IV0,0.11.0,0.11.0-IV0,0.11.0-IV1,0.11.0-IV2,0.8.0,0.8.1,0.8.2,0.9.0,1.0,1.0-IV0,1.1,1.1-IV0,2.0,2.0-IV0,2.0-IV1,2.1,2.1-IV0,2.1-IV1,2.1-IV2,2.2,2.2-IV0,2.2-IV1,2.3,2.3-IV0,2.3-IV1,2.4,2.4-IV0,2.4-IV1,2.5,2.5-IV0,2.6,2.6-IV0,2.7,2.7-IV0,2.7-IV1,2.7-IV2,2.8,2.8-IV0,2.8-IV1,3.0,3.0-IV0,3.0-IV1,3.1,3.1-IV0,3.2,3.2-IV0,3.3,3.3-IV0,3.3-IV1,3.3-IV2,3.3-IV3,3.4,3.4-IV0,3.5,3.5-IV0,3.5-IV1,3.5-IV2,3.6,3.6-IV0,3.6-IV1,3.6-IV2,3.7,3.7-IV0,3.7-IV1,3.7-IV2,3.7-IV3,3.7-IV4,3.8,3.8-IV0,3.9,3.9-IV0,3.9-IV1,4.0,4.0-IV0,4.1and4.1-IV0.
- messageTimestamp StringDifference Max Ms 
- The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if message.timestamp.type=LogAppendTime.
- messageTimestamp StringType 
- Define whether the timestamp in the message is message create time or log append time. The possible values are CreateTimeandLogAppendTime.
- minCleanable NumberDirty Ratio 
- This configuration controls how frequently the log compactor will attempt to clean the log (assuming log compaction is enabled). By default we will avoid cleaning a log where more than 50% of the log has been compacted. This ratio bounds the maximum space wasted in the log by duplicates (at 50% at most 50% of the log could be duplicates). A higher ratio will mean fewer, more efficient cleanings but will mean more wasted space in the log. If the max.compaction.lag.ms or the min.compaction.lag.ms configurations are also specified, then the log compactor considers the log to be eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records for at most the max.compaction.lag.ms period.
- minCompaction StringLag Ms 
- The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.
- minInsync StringReplicas 
- When a producer sets acks to 'all' (or '-1'), this configuration specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend). When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of 'all'. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.
- preallocate Boolean
- True if we should preallocate the file on disk when creating a new log segment.
- remoteStorage BooleanEnable 
- Indicates whether tiered storage should be enabled.
- retentionBytes String
- This configuration controls the maximum size a partition (which consists of log segments) can grow to before we will discard old log segments to free up space if we are using the 'delete' retention policy. By default there is no size limit only a time limit. Since this limit is enforced at the partition level, multiply it by the number of partitions to compute the topic retention in bytes.
- retentionMs String
- This configuration controls the maximum time we will retain a log before we will discard old log segments to free up space if we are using the 'delete' retention policy. This represents an SLA on how soon consumers must read their data. If set to -1, no time limit is applied.
- segmentBytes String
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentIndex StringBytes 
- This configuration controls the size of the index that maps offsets to file positions. We preallocate this index file and shrink it only after log rolls. You generally should not need to change this setting.
- segmentJitter StringMs 
- The maximum random jitter subtracted from the scheduled segment roll time to avoid thundering herds of segment rolling
- segmentMs String
- This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data. Setting this to a very low value has consequences, and the Aiven management plane ignores values less than 10 seconds.
- uncleanLeader BooleanElection Enable 
- Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.
GetKafkaTopicTag   
Package Details
- Repository
- Aiven pulumi/pulumi-aiven
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the aivenTerraform Provider.
