[
https://issues.apache.org/jira/browse/FLINK-19644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219082#comment-17219082
]
Leonard Xu commented on FLINK-19644:
------------------------------------
[~jark] Thanks for your clarification, "read.partition=max_partition()" is the
most common case and we can support this feature with Table Option way.
For SupportsPartitionPushDown to lookup source, the filter on lookup table has
been supported If every thing woks fine, this should be a prune optimization,
I agree that using `SupportsPartitionPushDown` is more insight way.
> Support read specific partition of Hive table in temporal join
> --------------------------------------------------------------
>
> Key: FLINK-19644
> URL: https://issues.apache.org/jira/browse/FLINK-19644
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Hive, Table SQL / Ecosystem
> Reporter: Leonard Xu
> Assignee: Leonard Xu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> It's a common case to use hive partitioned table as dimension table.
> Currently Hive table only supports load all data, It will be helpful if we
> can support read user specific partition in temporal table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
