DataStax Astra DB: NAMESPACE_DOES_NOT_EXIST on default_keyspace

TL;DR

Token role does not fix this: an Organization Administrator token still fails when the namespace is missing. The Data API call is pointed at a namespace that was never created in that database.

Fix

1. Token role does not fix this: an Organization Administrator token still fails when the namespace is missing. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this DataStax Astra DB feature.
• The symptom matches: NAMESPACEDOESNOTEXIST on defaultkeyspace.

When NOT to use

• Unrelated DataStax Astra DB issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against DataStax Astra DB. Source: https://github.com/langflow-ai/langflow/issues/1770.

Variant phrasings

NAMESPACEDOESNOTEXIST on defaultkeyspace

Why it happens

The Data API returns errors with errorCode NAMESPACEDOESNOTEXIST and message Unknown namespace defaultkeyspace, you must create it first.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/langflow-ai/langflow/issues/1770

Source: The Data API returns errors with errorCode NAMESPACEDOESNOTEXIST and message Unknown namespace defaultkeyspace, you must create it first.

Verified resolution: [langflow-ai/langflow issue]: the Data API call is pointed at a namespace that was never created in that database. Confirm the keyspace exists in the Astra DB console for that database, and that the app's namespace setting matches it exactly. A frequent cause in integrations is the app defaulting to default_keyspace while the database was created with a different keyspace. Token role does not fix this: an Organization Administrator token still fails when the namespace is missing.

Source URL: https://github.com/langflow-ai/langflow/issues/1770