You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jiabao Sun (Jira)" <ji...@apache.org> on 2023/06/27 12:11:00 UTC
[jira] [Commented] (FLINK-32446) MongoWriter should regularly check whether the last write time is greater than the specified time.
[ https://issues.apache.org/jira/browse/FLINK-32446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737621#comment-17737621 ]
Jiabao Sun commented on FLINK-32446:
------------------------------------
[~Leonard] Can you help assign this ticket to me?
> MongoWriter should regularly check whether the last write time is greater than the specified time.
> --------------------------------------------------------------------------------------------------
>
> Key: FLINK-32446
> URL: https://issues.apache.org/jira/browse/FLINK-32446
> Project: Flink
> Issue Type: Bug
> Components: Connectors / MongoDB
> Affects Versions: mongodb-1.0.0, mongodb-1.0.1
> Reporter: Jiabao Sun
> Priority: Major
>
> Mongo sink waits for new record to write previous records. I have a upsert-kafka topic filled that has already some events. I start a new upsert-kafka to mongo db sink job. I expect all the data from the topic to be loaded to mongodb right away. But instead, only the first record is written to mongo db. The rest of the records don’t arrive in mongodb until a new event is written to kafka topic. The new event that was written is delayed until the next event arrives.
> To prevent this problem, the MongoWriter should regularly check whether the last write time is greater than the specified time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)