You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/07/21 04:01:00 UTC

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

Jark Wu created FLINK-18654:
-------------------------------

             Summary: 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
            Reporter: Jark Wu


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. 





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