|
1 |
| -// ====== Generated from librdkafka 1.6.1 file CONFIGURATION.md ====== |
| 1 | +// ====== Generated from librdkafka 1.7.0 file CONFIGURATION.md ====== |
2 | 2 | // Code that generated this is a derivative work of the code from Nam Nguyen
|
3 | 3 | // https://gist.github.com/ntgn81/066c2c8ec5b4238f85d1e9168a04e3fb
|
4 | 4 |
|
@@ -62,13 +62,6 @@ export interface GlobalConfig {
|
62 | 62 | */
|
63 | 63 | "max.in.flight"?: number;
|
64 | 64 |
|
65 |
| - /** |
66 |
| - * Non-topic request timeout in milliseconds. This is for metadata requests, etc. |
67 |
| - * |
68 |
| - * @default 60000 |
69 |
| - */ |
70 |
| - "metadata.request.timeout.ms"?: number; |
71 |
| - |
72 | 65 | /**
|
73 | 66 | * Period of time in milliseconds at which topic and broker metadata is refreshed in order to proactively discover any new brokers, topics, partitions or partition leader changes. Use -1 to disable the intervalled refresh (not recommended). If there are no locally referenced topics (no topic objects created, no messages produced, no subscription or no assignment) then only the broker list will be refreshed every interval but no more often than every 10s.
|
74 | 67 | *
|
@@ -184,6 +177,13 @@ export interface GlobalConfig {
|
184 | 177 | */
|
185 | 178 | "broker.address.family"?: 'any' | 'v4' | 'v6';
|
186 | 179 |
|
| 180 | + /** |
| 181 | + * Close broker connections after the specified time of inactivity. Disable with 0. If this property is left at its default value some heuristics are performed to determine a suitable default value, this is currently limited to identifying brokers on Azure (see librdkafka issue #3109 for more info). |
| 182 | + * |
| 183 | + * @default 0 |
| 184 | + */ |
| 185 | + "connections.max.idle.ms"?: number; |
| 186 | + |
187 | 187 | /**
|
188 | 188 | * **DEPRECATED** No longer used. See `reconnect.backoff.ms` and `reconnect.backoff.max.ms`.
|
189 | 189 | *
|
@@ -403,8 +403,6 @@ export interface GlobalConfig {
|
403 | 403 |
|
404 | 404 | /**
|
405 | 405 | * File or directory path to CA certificate(s) for verifying the broker's key. Defaults: On Windows the system's CA certificates are automatically looked up in the Windows Root certificate store. On Mac OSX this configuration defaults to `probe`. It is recommended to install openssl using Homebrew, to provide CA certificates. On Linux install the distribution's ca-certificates package. If OpenSSL is statically linked or `ssl.ca.location` is set to `probe` a list of standard paths will be probed and the first one found will be used as the default CA certificate location path. If OpenSSL is dynamically linked the OpenSSL library's default path will be used (see `OPENSSLDIR` in `openssl version -a`).
|
406 |
| - * |
407 |
| - * @default probe |
408 | 406 | */
|
409 | 407 | "ssl.ca.location"?: string;
|
410 | 408 |
|
@@ -435,6 +433,23 @@ export interface GlobalConfig {
|
435 | 433 | */
|
436 | 434 | "ssl.keystore.password"?: string;
|
437 | 435 |
|
| 436 | + /** |
| 437 | + * Path to OpenSSL engine library. OpenSSL >= 1.1.0 required. |
| 438 | + */ |
| 439 | + "ssl.engine.location"?: string; |
| 440 | + |
| 441 | + /** |
| 442 | + * OpenSSL engine id is the name used for loading engine. |
| 443 | + * |
| 444 | + * @default dynamic |
| 445 | + */ |
| 446 | + "ssl.engine.id"?: string; |
| 447 | + |
| 448 | + /** |
| 449 | + * OpenSSL engine callback data (set with rd_kafka_conf_set_engine_callback_data()). |
| 450 | + */ |
| 451 | + "ssl_engine_callback_data"?: any; |
| 452 | + |
438 | 453 | /**
|
439 | 454 | * Enable OpenSSL's builtin broker (server) certificate verification. This verification can be extended by the application by implementing a certificate_verify_cb.
|
440 | 455 | *
|
@@ -708,7 +723,7 @@ export interface ConsumerGlobalConfig extends GlobalConfig {
|
708 | 723 | /**
|
709 | 724 | * Client group session and failure detection timeout. The consumer sends periodic heartbeats (heartbeat.interval.ms) to indicate its liveness to the broker. If no hearts are received by the broker for a group member within the session timeout, the broker will remove the consumer from the group and trigger a rebalance. The allowed range is configured with the **broker** configuration properties `group.min.session.timeout.ms` and `group.max.session.timeout.ms`. Also see `max.poll.interval.ms`.
|
710 | 725 | *
|
711 |
| - * @default 10000 |
| 726 | + * @default 45000 |
712 | 727 | */
|
713 | 728 | "session.timeout.ms"?: number;
|
714 | 729 |
|
@@ -966,14 +981,14 @@ export interface ProducerTopicConfig extends TopicConfig {
|
966 | 981 |
|
967 | 982 | export interface ConsumerTopicConfig extends TopicConfig {
|
968 | 983 | /**
|
969 |
| - * **DEPRECATED** [**LEGACY PROPERTY:** This property is used by the simple legacy consumer only. When using the high-level KafkaConsumer, the global `enable.auto.commit` property must be used instead]. If true, periodically commit offset of the last message handed to the application. This committed offset will be used when the process restarts to pick up where it left off. If false, the application will have to call `rd_kafka_offset_store()` to store an offset (optional). **NOTE:** There is currently no zookeeper integration, offsets will be written to broker or local file according to offset.store.method. |
| 984 | + * **DEPRECATED** [**LEGACY PROPERTY:** This property is used by the simple legacy consumer only. When using the high-level KafkaConsumer, the global `enable.auto.commit` property must be used instead]. If true, periodically commit offset of the last message handed to the application. This committed offset will be used when the process restarts to pick up where it left off. If false, the application will have to call `rd_kafka_offset_store()` to store an offset (optional). Offsets will be written to broker or local file according to offset.store.method. |
970 | 985 | *
|
971 | 986 | * @default true
|
972 | 987 | */
|
973 | 988 | "auto.commit.enable"?: boolean;
|
974 | 989 |
|
975 | 990 | /**
|
976 |
| - * **DEPRECATED** Alias for `auto.commit.enable`: [**LEGACY PROPERTY:** This property is used by the simple legacy consumer only. When using the high-level KafkaConsumer, the global `enable.auto.commit` property must be used instead]. If true, periodically commit offset of the last message handed to the application. This committed offset will be used when the process restarts to pick up where it left off. If false, the application will have to call `rd_kafka_offset_store()` to store an offset (optional). **NOTE:** There is currently no zookeeper integration, offsets will be written to broker or local file according to offset.store.method. |
| 991 | + * **DEPRECATED** Alias for `auto.commit.enable`: [**LEGACY PROPERTY:** This property is used by the simple legacy consumer only. When using the high-level KafkaConsumer, the global `enable.auto.commit` property must be used instead]. If true, periodically commit offset of the last message handed to the application. This committed offset will be used when the process restarts to pick up where it left off. If false, the application will have to call `rd_kafka_offset_store()` to store an offset (optional). Offsets will be written to broker or local file according to offset.store.method. |
977 | 992 | *
|
978 | 993 | * @default true
|
979 | 994 | */
|
|
0 commit comments