You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chanhae Oh (Jira)" <ji...@apache.org> on 2026/06/21 13:18:00 UTC

[jira] [Comment Edited] (FLINK-38046) Solve the issue of missing one piece of data

    [ https://issues.apache.org/jira/browse/FLINK-38046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18090430#comment-18090430 ] 

Chanhae Oh edited comment on FLINK-38046 at 6/21/26 1:17 PM:
-------------------------------------------------------------

Hi [~jingzi]!

I've opened a new PR (#198) to get this bugfix included in the upcoming flink-connector-jdbc release. You are and always will be the original author of this fix — thank you so much for the contribution.

If you happen to come back before #198 is merged, please feel free to continue with #174 instead.

Thank you !


was (Author: JIRAUSER311960):
Hi @jingzi,

I've opened a new PR (#198) to get this bugfix included in the upcoming flink-connector-jdbc release. You are and always will be the original author of this fix — thank you so much for the contribution.

If you happen to come back before #198 is merged, please feel free to continue with #174 instead.

Thank you !

> Solve the issue of missing one piece of data
> --------------------------------------------
>
>                 Key: FLINK-38046
>                 URL: https://issues.apache.org/jira/browse/FLINK-38046
>             Project: Flink
>          Issue Type: Bug
>            Reporter: jingzi
>            Priority: Major
>              Labels: pull-request-available
>
> When using partitioned scan in Flink JDBC table, if {{scan.partition.lower-bound}} and {{scan.partition.upper-bound}} are very large, there could be a situation where one data record is lost. For example, maximum value: 3875220057236942850, minimum value: 2260418954055131340.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)