Kafka Jdbc Connect timestamp+incrementing mode
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am using Kafka Jdbc Connect timestamp+incrementing mode to sync a table rows to Kafka. Reference https://docs.confluent.io/current/connect/connect-jdbc/docs/source_config_options.html#mode
The challenge is the table gets synced from the beginning of time since the start time by default is 1970. Is there any way to over ride the start time (i.e) I want to sync only from the beginning of input given date.
apache-kafka apache-kafka-connect
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
add a comment |
I am using Kafka Jdbc Connect timestamp+incrementing mode to sync a table rows to Kafka. Reference https://docs.confluent.io/current/connect/connect-jdbc/docs/source_config_options.html#mode
The challenge is the table gets synced from the beginning of time since the start time by default is 1970. Is there any way to over ride the start time (i.e) I want to sync only from the beginning of input given date.
apache-kafka apache-kafka-connect
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
add a comment |
I am using Kafka Jdbc Connect timestamp+incrementing mode to sync a table rows to Kafka. Reference https://docs.confluent.io/current/connect/connect-jdbc/docs/source_config_options.html#mode
The challenge is the table gets synced from the beginning of time since the start time by default is 1970. Is there any way to over ride the start time (i.e) I want to sync only from the beginning of input given date.
apache-kafka apache-kafka-connect
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
I am using Kafka Jdbc Connect timestamp+incrementing mode to sync a table rows to Kafka. Reference https://docs.confluent.io/current/connect/connect-jdbc/docs/source_config_options.html#mode
The challenge is the table gets synced from the beginning of time since the start time by default is 1970. Is there any way to over ride the start time (i.e) I want to sync only from the beginning of input given date.
apache-kafka apache-kafka-connect
apache-kafka apache-kafka-connect
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
asked Aug 1 '18 at 7:18
Vinod JayachandranVinod Jayachandran
1,54322042
1,54322042
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In case that you want to start from a given offset with your connector, I'd suggest overwriting the information stored in the connect-offsets topic.
Through the Kafka REST API you can easily read the content of this topic:
http://localhost:8082/topics/connect-offsets
Looking through the code of the kafka-connector-jdbc in the relevant methods for the use case that you've described:
- io.confluent.connect.jdbc.source.TimestampIncrementingCriteria#extractValues
- io.confluent.connect.jdbc.source.TimestampIncrementingOffset#getTimestampOffset
that overriding the connect-offsets topic content seems to be the only way available at the moment.
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
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%2f51627472%2fkafka-jdbc-connect-timestampincrementing-mode%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
In case that you want to start from a given offset with your connector, I'd suggest overwriting the information stored in the connect-offsets topic.
Through the Kafka REST API you can easily read the content of this topic:
http://localhost:8082/topics/connect-offsets
Looking through the code of the kafka-connector-jdbc in the relevant methods for the use case that you've described:
- io.confluent.connect.jdbc.source.TimestampIncrementingCriteria#extractValues
- io.confluent.connect.jdbc.source.TimestampIncrementingOffset#getTimestampOffset
that overriding the connect-offsets topic content seems to be the only way available at the moment.
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
add a comment |
In case that you want to start from a given offset with your connector, I'd suggest overwriting the information stored in the connect-offsets topic.
Through the Kafka REST API you can easily read the content of this topic:
http://localhost:8082/topics/connect-offsets
Looking through the code of the kafka-connector-jdbc in the relevant methods for the use case that you've described:
- io.confluent.connect.jdbc.source.TimestampIncrementingCriteria#extractValues
- io.confluent.connect.jdbc.source.TimestampIncrementingOffset#getTimestampOffset
that overriding the connect-offsets topic content seems to be the only way available at the moment.
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
add a comment |
In case that you want to start from a given offset with your connector, I'd suggest overwriting the information stored in the connect-offsets topic.
Through the Kafka REST API you can easily read the content of this topic:
http://localhost:8082/topics/connect-offsets
Looking through the code of the kafka-connector-jdbc in the relevant methods for the use case that you've described:
- io.confluent.connect.jdbc.source.TimestampIncrementingCriteria#extractValues
- io.confluent.connect.jdbc.source.TimestampIncrementingOffset#getTimestampOffset
that overriding the connect-offsets topic content seems to be the only way available at the moment.
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
In case that you want to start from a given offset with your connector, I'd suggest overwriting the information stored in the connect-offsets topic.
Through the Kafka REST API you can easily read the content of this topic:
http://localhost:8082/topics/connect-offsets
Looking through the code of the kafka-connector-jdbc in the relevant methods for the use case that you've described:
- io.confluent.connect.jdbc.source.TimestampIncrementingCriteria#extractValues
- io.confluent.connect.jdbc.source.TimestampIncrementingOffset#getTimestampOffset
that overriding the connect-offsets topic content seems to be the only way available at the moment.
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
answered Nov 16 '18 at 12:15
marius_neomarius_neo
7761624
7761624
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.
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%2f51627472%2fkafka-jdbc-connect-timestampincrementing-mode%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
