> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduktor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Kafka protocol support

> Turn Kafka protocol features on or off in Conduktor Gateway, such as topic IDs, incremental fetch sessions and the KIP-848 consumer group protocol.

Kafka adds features to its protocol through Kafka Improvement Proposals (KIPs). You can turn these features on or off in Gateway with a feature flag on every Gateway node:

| Feature | KIP | Default | Environment variable |
| - | - | - | - |
| [Topic IDs](#topic-id-support) | [KIP-516](https://cwiki.apache.org/confluence/display/KAFKA/KIP-516%3A+Topic+Identifiers) | On | `GATEWAY_FEATURE_FLAGS_TOPIC_ID_SUPPORT` |
| [Incremental fetch sessions](#incremental-fetch-sessions) | [KIP-227](https://cwiki.apache.org/confluence/display/KAFKA/KIP-227%3A+Introduce+Incremental+FetchRequests+to+Increase+Partition+Scalability) | On | `GATEWAY_FEATURE_FLAGS_INCREMENTAL_FETCH_SESSIONS_ENABLED` |
| [Consumer group protocol](#consumer-group-protocol) (preview) | [KIP-848](https://cwiki.apache.org/confluence/display/KAFKA/KIP-848%3A+The+Next+Generation+of+the+Consumer+Rebalance+Protocol) | Off | `GATEWAY_FEATURE_FLAGS_CONSUMER_GROUP_PROTOCOL` |

## Topic IDs

Clients can identify topics by ID instead of by name in these API versions:

| API | Versions that use topic IDs | Highest version with topic IDs off |
| - | - | - |
| Fetch | v13 and later | v12 |
| Produce | v13 and later | v12 |
| Metadata | v12 and later | v11 |
| DeleteTopics | v6 and later | v5 |
| OffsetCommit | v10 and later | v9 |
| OffsetFetch | v10 and later | v9 |

To turn topic IDs off, set `GATEWAY_FEATURE_FLAGS_TOPIC_ID_SUPPORT=false`. The [consumer group protocol](#consumer-group-protocol) needs topic IDs, so it then stays off.

## Incremental fetch sessions

With incremental fetch sessions, a consumer sends a first, full Fetch request, then only the partitions that changed, which makes Fetch requests smaller.

To turn incremental fetch sessions off, set `GATEWAY_FEATURE_FLAGS_INCREMENTAL_FETCH_SESSIONS_ENABLED=false`. Turn them off if you use the [cache Interceptor](https://docs.conduktor.io/guide/use-cases/cache-kafka-data.md): consumers reading through it can stop receiving records.

> [!NOTE]
>
> If you use the [audit Interceptor](https://docs.conduktor.io/guide/reference/data-security.md#audit-interceptor) or a [fetch policy](https://docs.conduktor.io/guide/use-cases/apply-traffic-control-policies.md#fetch-policy), incremental fetch sessions change how they behave. See those pages for details.

## Consumer group protocol

The consumer group protocol lets consumers use `group.protocol=consumer`, where the broker computes the partition assignment. [Find out how to use the consumer group protocol](https://docs.conduktor.io/guide/conduktor-in-production/deploy-artifacts/deploy-gateway/consumer-group-protocol.md).

## Related resources

* [Gateway environment variables](https://docs.conduktor.io/guide/conduktor-in-production/deploy-artifacts/deploy-gateway/environment-variables.md#feature-flags)
* [Feature labels](https://docs.conduktor.io/guide/reference/feature-labels.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.