You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/12/19 14:49:00 UTC

[jira] [Closed] (FLINK-19905) The Jdbc-connector's 'lookup.max-retries' option initial value is 1 in JdbcLookupFunction

     [ https://issues.apache.org/jira/browse/FLINK-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jark Wu closed FLINK-19905.
---------------------------
    Resolution: Fixed

Fixed in master: cc9ccc42e8c8f7221c6d35f4c011d573577d0505

> The Jdbc-connector's 'lookup.max-retries' option initial value is 1 in JdbcLookupFunction
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-19905
>                 URL: https://issues.apache.org/jira/browse/FLINK-19905
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / JDBC
>    Affects Versions: 1.11.2, 1.11.3
>            Reporter: dalongliu
>            Assignee: jiawen xiao
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> As describe in FLINK-19684, we should init the begin value to 0 in JdbcLookupFunction. The PR only correct the retry value to 0 in JdbcRowDataLookupFunction and JdbcBatchingOutputFormat class, maybe the contributor forgets to correct it in JdbcLookupFunction class.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)