Since this PR requires changes to the SPI (io.trino.spi.connector.SystemTable), I'm wondering how to approach them. Should I introduce a new cursor method to the SystemTable interface? Currently, I have extended an existing one.
Additional context and related issues
Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:
## Section
* Fix some things. ({issue}`issuenumber`)
Description
This PR implements parallelization of table retrieval at the catalog level by generating a split for each catalog.
Benchmark results for the following query (9 catalogs, 822 schemas, 17835 tables):
The chart compares the execution time of the query above between
masterand the changes introduced in this PR and https://github.com/trinodb/trino/pull/24110.Question
Since this PR requires changes to the SPI (
io.trino.spi.connector.SystemTable), I'm wondering how to approach them. Should I introduce a newcursormethod to theSystemTableinterface? Currently, I have extended an existing one.Additional context and related issues
Release notes
( ) This is not user-visible or is docs only, and no release notes are required. ( ) Release notes are required. Please propose a release note for me. ( ) Release notes are required, with the following suggested text: