[
https://issues.apache.org/jira/browse/FLINK-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327884#comment-17327884
]
Flink Jira Bot commented on FLINK-17360:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Support custom partitioners in JDBCReadOptions
> -----------------------------------------------
>
> Key: FLINK-17360
> URL: https://issues.apache.org/jira/browse/FLINK-17360
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Flavio Pompermaier
> Priority: Major
> Labels: stale-major
>
> Suport custom ParameterValuesProvider. At the moment only
> NumericBetweenParametersProvider is handled if a partition column and min/max
> values are specified.
> In a discussion in the mailing list some discussion about this was made.
> Me ([~f.pompermaier]):
> Then we can add a *scan.parametervalues.provider.class* in order to customize
> the splitting of the query (we can also add a check that the query contains
> at least 1 question mark).
> If we introduce a custom parameters provider we need also to specify
> parameters, using something like:
> 'scan.parametervalues.0.name' = 'minDate',
> 'scan.parametervalues.0.value'= '12/10/2019'
> 'scan.parametervalues.1.name' = 'maxDate',
> 'scan.parametervalues.1.value'= '01/01/2020'
> [~lzljs3620320]
> Maybe we need add something like "scan.parametervalues.provider.type", it can
> be "bound, specify, custom":
> - when *bound*, using old p*artitionLowerBound* and *partitionUpperBound*,
> *numPartitions*
> - when *specify*, using specify parameters like your proposal
> - when *custom*, need *scan.parametervalues.provider.class*
> Actually I don't know if specify and custom can be separated..but this can be
> further discussed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
