-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
ALL
This is a call to prevent the creation of databases or collections with illegal names.
During a recent training, some of the trainees ran into a problem when we were doing backups using mongodump. mongodump stopped, giving an error message because it couldn't dump a database named "*". "show dbs" in the shell confirmed that there was indeed a database named "*". (But attempting to use it failed because that led to a "..." continuation prompt.) But only a few people were affected, so this doesn't appear to be systemic. It seems likely that this was created accidentally as a result of some earlier mistyped command, possibly an attempt to use a wild card incorrectly.
In some contexts, this name worked, and in others it didn't, leading me to believe we're not validating these on the server, but are instead relying on client parsers to keep them out, but apparently not always successfully.
- depends on
-
SERVER-4229 mongodump creates a database named * (asterisk) that cannot subsequently be deleted
- Closed
- duplicates
-
SERVER-4584 mongod crashes when trying to create a collection in a database *
- Closed
- is duplicated by
-
SERVER-5248 CLONE - Mongodump error: "error: boost::filesystem::create_directory: The filename, directory name, or volume label syntax is incorrect" while exporting collection "*"
- Closed
- is related to
-
SERVER-4302 user shouldn't be able to create collection having a name prefixed by 'system.'
- Closed
-
SERVER-5002 Change prohibited character sets in database names
- Closed