I am trying to load the sample data of 350 MB on 06/08/2024.
Ended up with the Error “An error occurred loading sample data: Target cluster has conflicting non-empty namespace with the dataset”
Cluster: hrk243
Version: 7.0.12
Region: AWS / N. Virginia (us-east-1)
Cluster Tier: M0 Sandbox (General)
Type: Replica Set - 3 nodes
Backups: Inactive
Linked App Services: None Linked
https://cloud.mongodb.com/v2/66cb5bd0d1dd0f4ac8febc8c#/clusters
Welcome to the MongoDB Community! 
I suggest you create a new cluster and load a sample dataset into it or check datasets in your current cluster. You should check this:
Best,
Shreya
@shreya_patel I would like to share my similar experience with this. It seems to me that new MongoDB clusters now come with sample_mflix by default. However, since this same sample dataset is also included in the 350mb sample data, the namespace conflict happens since sample_mflix already exists. Strangely I have seen via team members that they had a different UI: a dropdown menu where the option was given to choose via checklist which sample data to install. In their case the bug was avoided. However as of today the option remains in my account to install the full 350mb set, and thus the error also persists. I wish you would give everyone the dropdown do avoid this headache.
Hi
I am still getting the same error. Not sure how to get around it.
I was following the tutorial here:
are you saying i should be selecting a sample dataset from somewhere else? I don’t think I can upload my own sample
| Topic | Replies | Views | Activity |
|---|---|---|---|
| $setWindowFields is slow to $rank | 2 | 555 | May 2024 |
| AWS Bedrock Knowledge Bases + MongoDB Atlas Failure | 2 | 707 | Jun 2024 |
| allowDiskUse: true not working for serverless instance | 5 | 422 | Jan 28 |
| Connect to MongoDB Atlas from Google CloudRun | 2 | 253 | Sep 2024 |
| Merge two collections in real time with kafka connector | 0 | 32 | Dec 2024 |
