Kstream how it manage joins and topic expiration
I need ask a question to get some clarification.
Let's assume this scenario: topic1 and topic2 are 2 tables of same database, table1 have a high amount of updates/insert, table2 is standard almost never updated. Let's assume also that we have a streaming that join the 2 tables
After 3-6 months what will happen to the join of the 2 tables?
What i am expecting is that at a certain time Kafka will empty topic2 because there are no updates so I think that the join wil always return null
how kafka will manage this kind of situation?
apache-kafka apache-kafka-streams
add a comment |
I need ask a question to get some clarification.
Let's assume this scenario: topic1 and topic2 are 2 tables of same database, table1 have a high amount of updates/insert, table2 is standard almost never updated. Let's assume also that we have a streaming that join the 2 tables
After 3-6 months what will happen to the join of the 2 tables?
What i am expecting is that at a certain time Kafka will empty topic2 because there are no updates so I think that the join wil always return null
how kafka will manage this kind of situation?
apache-kafka apache-kafka-streams
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47
add a comment |
I need ask a question to get some clarification.
Let's assume this scenario: topic1 and topic2 are 2 tables of same database, table1 have a high amount of updates/insert, table2 is standard almost never updated. Let's assume also that we have a streaming that join the 2 tables
After 3-6 months what will happen to the join of the 2 tables?
What i am expecting is that at a certain time Kafka will empty topic2 because there are no updates so I think that the join wil always return null
how kafka will manage this kind of situation?
apache-kafka apache-kafka-streams
I need ask a question to get some clarification.
Let's assume this scenario: topic1 and topic2 are 2 tables of same database, table1 have a high amount of updates/insert, table2 is standard almost never updated. Let's assume also that we have a streaming that join the 2 tables
After 3-6 months what will happen to the join of the 2 tables?
What i am expecting is that at a certain time Kafka will empty topic2 because there are no updates so I think that the join wil always return null
how kafka will manage this kind of situation?
apache-kafka apache-kafka-streams
apache-kafka apache-kafka-streams
edited Nov 14 '18 at 15:41
cricket_007
82.8k1144112
82.8k1144112
asked Nov 14 '18 at 9:54
SanoSano
589
589
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47
add a comment |
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47
add a comment |
0
active
oldest
votes
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%2f53297344%2fkstream-how-it-manage-joins-and-topic-expiration%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53297344%2fkstream-how-it-manage-joins-and-topic-expiration%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
The join window would need adjusted to capture all events needing joined, but the Kafka topic itself has its own retention policies, so if you don't want deleted messages, maybe increase the retention? Kafka doesn't "manage" if data comes from external systems, or not, so this seems very specific to be implemented within some Kafka Streams logic (or don't use Streams, and use Connect to sink data from individual topics into a separate system where you will join events)
– cricket_007
Nov 14 '18 at 15:44
You should use log compacted topics instead of retention based topics.
– Matthias J. Sax
Nov 14 '18 at 23:46
@MatthiasJ.Sax can you provide me more details about this?
– Sano
Nov 15 '18 at 9:51
kafka.apache.org/documentation/#compaction
– Matthias J. Sax
Nov 15 '18 at 19:47