✦TL;DR

Frequently asked questions about CrateDB connector setup, permissions, and limitations

||

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

How do I make sure Atlan can access new tables automatically?

CrateDB requires explicit permission configuration to access tables created after initial setup.

• Grant schema-level permissions (recommended): This approach automatically includes all future tables:

  GRANT DQL ON SCHEMA doc TO atlan_user;

  This single command covers all current and future tables in the schema, including metadata access.

• Grant wildcard permissions: Use this for specific table patterns:

  GRANT DQL ON TABLE doc.* TO atlan_user;

• Regular permission audits: Since CrateDB has limited stored procedure support, consider regular permission audits:

  -- Check current user permissions
  SELECT privilege_type, table_schema, table_name 
  FROM information_schema.table_privileges 
  WHERE grantee = 'atlan_user'
  ORDER BY table_schema, table_name;

What CrateDB limitations affect the Atlan connector?

• No explicit schema creation: CrateDB doesn't support the CREATE SCHEMA statement. Schemas are created implicitly when a table referencing a new schema is created.

• No metadata-only access: CrateDB’s DQL privileges apply to both metadata and data. This means the Atlan user can view and query all data in any tables they have permission to access.

• Limited automation: CrateDB doesn't support triggers or full stored procedure capabilities, which restricts options for automating permission management or other operational tasks.