Closed herefree closed 1 week ago
Hi @herefree , can you explain what is the difference?
Hi @herefree , can you explain what is the difference?
Before, in flink, every time we get partition, we need to get it from readBuilder.newScan().listPartitionEntries()
. After modification, we get partitions from Catalog.listPartitions. If Catalog is CachingCatalog, we can get partitions in cache.
Hi @herefree , can you explain what is the difference?
Before, in flink, every time we get partition, we need to get it from
readBuilder.newScan().listPartitionEntries()
. After modification, we get partitions from Catalog.listPartitions. If Catalog is CachingCatalog, we can get partitions in cache.
Really? How to get partitions from cache? It seems that you do not modify the CachingCatalog
.
Hi @herefree , can you explain what is the difference?
Before, in flink, every time we get partition, we need to get it from
readBuilder.newScan().listPartitionEntries()
. After modification, we get partitions from Catalog.listPartitions. If Catalog is CachingCatalog, we can get partitions in cache.Really? How to get partitions from cache? It seems that you do not modify the
CachingCatalog
.
I found that we have implemented partitionCache in CacheCatalog. I found a problem. There is no place to refresh the partition in Flink. Sorry,maybe I should turn off this feature.
Purpose
Flink listPartitions from catalog.listPartitions, caching catalog can increase acquisition speed of partition.
Linked issue: close #xxx
Tests
API and Format
Documentation