Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: support additional characters allowed in keys #1664

Open
jinzishuai opened this issue Nov 7, 2024 · 2 comments · May be fixed by #1762
Open

Feature Request: support additional characters allowed in keys #1664

jinzishuai opened this issue Nov 7, 2024 · 2 comments · May be fixed by #1762

Comments

@jinzishuai
Copy link

jinzishuai commented Nov 7, 2024

In comparison with other products,

  • MongoDB natively allows a user to write the full kubernetes manifest json into a document, including ., / and -. For example, a very commonly seen label looks like
app.kubernetes.io/managed-by: kustomize

Amazon DocumentDB does not support dots “.” in a document field name, for example, db.foo.insert({‘x.1’:1}).
Amazon DocumentDB also does not support the $ prefix in field names.

Can contain uppercase letters A-Z, lowercase letters a-z, numbers 0-9, and underscores (_).

Minimal Request

Given the difficulty of ., we request adding support to at least / and -. We are currently using AWS DocumentDB and have already implemented a transformation for . . Supporting / and - in Data API would make it possible for us to migrate to use AstraDB.

@amorton
Copy link
Contributor

amorton commented Nov 7, 2024

thanks, related to #1120

will reach out to get some more details, we know we need to open this up to almost everything. We will do it to align the field names across both Collections and Tables (the iterop with CQL)

@tatu-at-datastax
Copy link
Contributor

Note: provided a temporary build (v1.0.20-ct1) for Docker image that supports this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants