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

zhanghuaibei commented on FLINK-21820:
--------------------------------------

h4. [~leonard] [~jark] [~yangsanity] [~nicholasjiang] 

 Is fetchsize not effective yet? In version 3.2 of mysqlcdc, 
usecursorfetch=true has been set, but when chunksize is set to 4, it still 
causes room error

> JDBC connector shouldn't read all rows in per statement by default
> ------------------------------------------------------------------
>
>                 Key: FLINK-21820
>                 URL: https://issues.apache.org/jira/browse/FLINK-21820
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / JDBC, Table SQL / Ecosystem
>            Reporter: Leonard Xu
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> The default value for JDBC option 'scan.fetch-size' is 0 which means read all 
> rows in statement, this may lead to OOM or IO timeout.
> We'd better set a reasonable value as default value.
>  
>  



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

Reply via email to