Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hey folks, Happy new year! I want to bump this thread with the freshed PR #11845 . I've applied the recommendations from this thread. The PR replaces examples of Hadoop catalog in the Getting Started pages with the JDBC Catalog along with an added exam

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hey Kevin, This approach sounds good to me and thanks for your work to improve the getting started docs! I would consider using the file-based sqlite rather than in-memory since I've seen some users surprised when they realize their tables disappear from the catalog upon restart, but either way i

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hi Kevin It sounds reasonable to me. I would just mention that the REST catalog is the preferred one. Regards JB On Wed, Oct 16, 2024 at 8:40 PM Kevin Liu wrote: > > Hey folks, > > > Thanks for the discussions. > > > It seems everyone is in favor of replacing the Hadoop catalog example, and >

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hi: Here's what I propose as a middle-ground. > >1. We replace the Hadoop catalog example with a JDBC catalog backed by >an in-memory datastore. This allows users to get started without needing >additional infrastructure, which was one of the main benefits of the Hadoop >catalog. >

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hey folks, Thanks for the discussions. It seems everyone is in favor of replacing the Hadoop catalog example, and the question now is whether to replace it with the JDBC catalog or the REST catalog. I originally proposed the JDBC catalog as a replacement primarily due to its ease of use. User

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

I would prefer to advocate for the REST catalog in those examples/docs (similar to how the Spark quickstart example uses the REST catalog). The docs could then refer to the quickstart example to indicate what's required in terms of services to be start

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hi As we are talking about "documentation" (quick start/readme), I would rather propose to use the REST catalog here instead of JDBC. As it's the catalog we "promote", I think it would be valuable for users to start with the "right thing". JDBC Catalog is interesting for quick test/started guide

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

I would also vote for jdbc catalog, ideally using sqlite as backend as it doesn't require setting up other databases. On Thu, Oct 10, 2024 at 8:42 AM Manu Zhang wrote: > I'd vote for JDBC catalog as it's simple for a quick-start guide. Setting > up a REST Service with docker image could be cumbe

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

I'd vote for JDBC catalog as it's simple for a quick-start guide. Setting up a REST Service with docker image could be cumbersome. We can have another page for REST Catalog. Regards, Manu On Thu, Oct 10, 2024 at 2:50 AM Marc Cenac wrote: > I support the idea of updating the docs to replace the

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

I support the idea of updating the docs to replace the Hadoop catalog example, but I'm wondering why not use a REST Catalog example instead? I saw Ajantha proposed adding Docker images for a REST Catalog adapter [1] so we could potentially use this with a JDBC Catalog backed by SQLite file as a co

[Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

Hi all, I wanted to bring up a suggestion regarding our current documentation. The existing examples for Iceberg often use the Hadoop catalog, as seen in: - Adding a Catalog - Spark Quickstart [1] - Adding Catalogs - Spark Getting Started [2] Since we generally advise against using Hadoop