Multi-Catalog Server Support coming soon!

[VGSML]

We are going to add support for serving multiple catalogs from a single Airport Flight server endpoint.

Features

Multi-Catalog Routing

• Serve multiple named catalogs from a single gRPC endpoint
• Route requests based on airport-catalog gRPC metadata header
• Default catalog routing when no header is provided (empty name catalog)

Dynamic Catalog Management

• Add catalogs at runtime with MultiCatalogServer.AddCatalog()
• Remove catalogs at runtime with MultiCatalogServer.RemoveCatalog()
• Thread-safe operations for concurrent access

Per-Catalog Authorization

• New auth.CatalogAuthorizer interface for catalog-level access control
• Separates authentication (who are you?) from authorization (can you access this catalog?)
• Called automatically after successful authentication

Context Metadata

• flight.CatalogNameFromContext() - get target catalog from request
• flight.TraceIDFromContext() - distributed tracing support
• flight.SessionIDFromContext() - client session tracking

Usage

  config := airport.MultiCatalogServerConfig{
      Catalogs: []catalog.Catalog{salesCatalog, analyticsCatalog},
      Auth:     myCatalogAwareAuth, // Optional: implements CatalogAuthorizer
  }

  opts := airport.MultiCatalogServerOptions(config)
  grpcServer := grpc.NewServer(opts...)

  mcs, err := airport.NewMultiCatalogServer(grpcServer, config)

  // Dynamic management at runtime
  mcs.AddCatalog(newCatalog)
  mcs.RemoveCatalog("catalog-name")

Breaking Changes

None - this is an additive feature.

Note

The airport-catalog header support in DuckDB Airport extension is pending. Server-side implementation is complete and tested.