Most of the development of REST catalog comes from Tabular at this moment, I will let them comment more about this.
Speaking from AWS perspective, we have been recommending REST catalog for organizations that have their internal in house catalog systems. The REST catalog provides a really well-designed and standardized API spec that organizations can translate requests to and from their existing catalog system, so that it can (1) work with Iceberg tables, or (2) even translate their non-Iceberg tables to be exposed as an Iceberg table for query, so they can standardize their readers and writers just to Iceberg and reduce maintenance burden of multiple readers and writers of different table and file formats. I cannot say ONLY for new feature development, because for example we will likely continue to support AWS Glue catalog integration and it has an active roadmap. But the interest in REST is overall strong compared to the other catalog types like Hive, JDBC and DynamoDB. Best, Jack Ye On Thu, Feb 9, 2023 at 1:24 PM Xinyi Lu <[email protected]> wrote: > Hi Community, > > We’ve been evaluating the RestCatalog and want to know your feedback on > what’s the best scenarios for using RestCatalog and the current adoption > status in the industry. Will this be the iceberg catalog standard going > forward to encourage users to move metadata transactions to the server > side? Are we looking to adding more features which are only supported by > the RestCatalog? > > > > Thanks, > Xinyi
