[jira] [Closed] (FLINK-18654) Correct missleading documentation in "Partitioned Scan" section of JDBC connector

["Jark Wu (Jira)" <ji...@apache.org>]

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

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

Fixed in master: 596bba9a7cda02ffae1606579ee016a58cf46a1d

> Correct missleading documentation in "Partitioned Scan" section of JDBC connector
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-18654
>                 URL: https://issues.apache.org/jira/browse/FLINK-18654
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / JDBC, Documentation, Table SQL / Ecosystem
>    Affects Versions: 1.11.0
>            Reporter: Jark Wu
>            Assignee: jiawen xiao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0, 1.11.4
>
>
> In https://ci.apache.org/projects/flink/flink-docs-master/dev/table/connectors/jdbc.html#partitioned-scan
> > Notice that scan.partition.lower-bound and scan.partition.upper-bound are just used to decide the partition stride, not for filtering the rows in table. So all rows in the table will be partitioned and returned.
> The "not for filtering the rows in table" is not correct, actually, if partition bounds is defined, it only scans rows in the bound range. 
> Besides, maybe it would be better to add some practice suggestion, for example, 
> "If it is a batch job, I think it also doable to get the max and min value first before submitting the flink job."



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