[SERVER-76793] Warn when database names are invalid UTF-8 Created: 03/May/23  Updated: 06/Jun/23  Resolved: 06/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Maria van Keulen Assignee: Backlog - Query Execution
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by TOOLS-3286 Investigate changes in SERVER-75942: ... Waiting (Blocked)
Duplicate
duplicates SERVER-75942 Check that database name is valid UTF... Open
Related
is related to SERVER-75942 Check that database name is valid UTF... Open
Assigned Teams:
Query Execution
Participants:

 Description   

See SERVER-75942 for an example where a database can have invalid UTF-8. The current proposal for SERVER-75942 is to disallow creation of databases with invalid UTF-8 names. It'd be great if we could also provide users with the ability to check if any existing database names are invalid UTF-8.



 Comments   
Comment by Xiaochen Wu [ 06/Jun/23 ]

We will check the invalid names and block upgrade when implementing SERVER-75942. I don't think we need any other checks or warnings. The user can always query their database names and check. Closing it as dup with SERVER-75942.

Comment by Dave Rolsky [ 03/May/23 ]

I would note that we could do this by giving users some sort of script to run against their MongoDB installations. It could enumerate all the namespaces and check if they're valid UTF-8. This should be quite easy to write in any of a number of languages. If we wanted to make it even easier for users, we could build this in Go (or Rust) and distribute a single-file executable for a variety of platforms.

Generated at Thu Feb 08 06:33:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.