Proposal: Removal of Namespace terminology in Data API #1373
jeffreyscarpenter
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Background
When we designed the Data API, we attempted to abstract many Cassandra-specific details to make the API simpler to use. Among other choices, we preserved the concept of a group of containers or tables, but decided to call it a namespace instead of a keyspace. There was discussion of removing the concept of a keyspace/namespace entirely but this would have caused other issues. Because of this, we’ve found ourselves adding additional complexity to the concept by having to call them out together, but explain there is no difference between the two creating unnecessary cognitive overload for developers.
This is made worse for Data API users in DataStax Astra by the fact that we create a “default_keyspace” in Astra but then refer to it as a namespace in the portal, which looks quite odd and is confusing to developers.
Proposal
The concept of a container for document collections remains, and is not something we want to try to abstract. Instead of trying to substitute a different term “namespace”, we will revert to using the Cassandra standard term “keyspace”. We will do this in a way that is backwards compatible and minimizes impact and developer confusion.
The following changes are recommended:
Beta Was this translation helpful? Give feedback.
All reactions