XN137 opened a new issue, #2352: URL: https://github.com/apache/polaris/issues/2352
### Is your feature request related to a problem? Please describe. in https://github.com/apache/polaris/pull/2317 a TODO got added to the jdbc persistence implementation: https://github.com/apache/polaris/blob/a8ca16b65bd0dcc013a4fc715b4111202b912c15/persistence/relational-jdbc/src/main/java/org/apache/polaris/persistence/relational/jdbc/JdbcBasePersistenceImpl.java#L424-L443 currently the method is simply forwarding to the non-optimized `listEntities` variant. ### Describe the solution you'd like the idea is that in the JDBC query we should only load the columns/properties needed for creating a `EntityNameLookupRecord` instance. the more general `listEntities` variant can be used as a starting point and trimmed down to just the necessary parts. also according to this [review comment](https://github.com/apache/polaris/pull/2317#discussion_r2271168766) we should make sure that the query in the optimized case can be served efficiently from the database by only having to read a single index (that contains all necessary columns) without having to access the main table/row storage. this may require a new or updated schema for the jdbc backend. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
