Kafka Streams: topic.compression.type not a known config
Adding the compression configuration in Kafka Streams, similarly as in this link:
properties.put(StreamsConfig.topicPrefix(TopicConfig.COMPRESSION_TYPE_CONFIG), "snappy");
but I see the following WARN messages in the log:
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
Is this setting not honored? Is it not well expressed?
java apache-kafka apache-kafka-streams
edited Nov 20 at 23:11
cricket_007
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
add a comment |
Adding the compression configuration in Kafka Streams, similarly as in this link:
properties.put(StreamsConfig.topicPrefix(TopicConfig.COMPRESSION_TYPE_CONFIG), "snappy");
but I see the following WARN messages in the log:
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
Is this setting not honored? Is it not well expressed?
java apache-kafka apache-kafka-streams
edited Nov 20 at 23:11
cricket_007
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
add a comment |
Adding the compression configuration in Kafka Streams, similarly as in this link:
properties.put(StreamsConfig.topicPrefix(TopicConfig.COMPRESSION_TYPE_CONFIG), "snappy");
but I see the following WARN messages in the log:
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
Is this setting not honored? Is it not well expressed?
java apache-kafka apache-kafka-streams
edited Nov 20 at 23:11
cricket_007
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
Adding the compression configuration in Kafka Streams, similarly as in this link:
properties.put(StreamsConfig.topicPrefix(TopicConfig.COMPRESSION_TYPE_CONFIG), "snappy");
but I see the following WARN messages in the log:
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,158] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.admin.AdminClientConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,194] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,209] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2018-11-19 23:52:10,221] WARN The configuration 'topic.compression.type' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
Is this setting not honored? Is it not well expressed?
java apache-kafka apache-kafka-streams
java apache-kafka apache-kafka-streams
edited Nov 20 at 23:11
cricket_007
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
edited Nov 20 at 23:11
cricket_007
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
edited Nov 20 at 23:11
cricket_007
78.8k1142109
edited Nov 20 at 23:11
cricket_007
78.8k1142109
edited Nov 20 at 23:11
cricket_007
78.8k1142109
78.8k1142109
asked Nov 20 at 21:27
xmar
359113
asked Nov 20 at 21:27
xmar
359113
asked Nov 20 at 21:27
xmar
359113
359113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can ignore those warnings. The "problem" is, that the topic config parameter is copied into the configs of the internally used clients and they don't know the parameter name and thus WARN about it. However, those configs must be set on the clients, because the clients will "forward" those configs to other parts in the code base that know how to use them.
It's a little unfortunate and a known issue (but not easy to address).
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401814%2fkafka-streams-topic-compression-type-not-a-known-config%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can ignore those warnings. The "problem" is, that the topic config parameter is copied into the configs of the internally used clients and they don't know the parameter name and thus WARN about it. However, those configs must be set on the clients, because the clients will "forward" those configs to other parts in the code base that know how to use them.
It's a little unfortunate and a known issue (but not easy to address).
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
add a comment |
You can ignore those warnings. The "problem" is, that the topic config parameter is copied into the configs of the internally used clients and they don't know the parameter name and thus WARN about it. However, those configs must be set on the clients, because the clients will "forward" those configs to other parts in the code base that know how to use them.
It's a little unfortunate and a known issue (but not easy to address).
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
add a comment |
You can ignore those warnings. The "problem" is, that the topic config parameter is copied into the configs of the internally used clients and they don't know the parameter name and thus WARN about it. However, those configs must be set on the clients, because the clients will "forward" those configs to other parts in the code base that know how to use them.
It's a little unfortunate and a known issue (but not easy to address).
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
You can ignore those warnings. The "problem" is, that the topic config parameter is copied into the configs of the internally used clients and they don't know the parameter name and thus WARN about it. However, those configs must be set on the clients, because the clients will "forward" those configs to other parts in the code base that know how to use them.
It's a little unfortunate and a known issue (but not easy to address).
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
answered Nov 20 at 22:20
Matthias J. Sax
28.1k34572
28.1k34572
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401814%2fkafka-streams-topic-compression-type-not-a-known-config%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
