I would like to contribute this issue, can assign it to me

now flussAdmin.listPartitionInfos only return the partition value, missing partition key. Flink require return a map contains partition key and value.so it's must be blocked by #195

@Alibaba-HZY you can get the partition keys from the Table#getDescriptor(). You can implement partition pushdown for single partition key first, so it is not blocked by #195.

For multiple partition pushdown, yes, we need to extend Admin#listPartitionInfos to return a map of partition keys and values. That can be done in/after #195.

@wuchong partition pushdown be executed only in batch mode?if so now batch mode only support datalake enabled or point queries on primary key.

After the discussion with @luoyuxia
in stream mode :we cannot determine the correct number of partitions such as table has three partitions ds=11 ds=12 ds=13, sql :select * from table where ds > 10, applyPartition input ds=11 ds=12 ds=13,then sourceEnumerator will recieve this, but the user might write ds=14.sourceEnumerator will not get ds=14.
in batch mode :only support datalake enabled or point queries on primary key,#40
is not closed.
So I think the partitionPushDown will not take effect

@Alibaba-HZY yes. for batch mode, we have to wait #40, and for streaming mode, we need to leverage SupportsFilterPushDown instead of SupportsPartitionPushDown. For example, if there is a where ds > 10, then you don't need to read partition from 0 to 10.