Description
When uploading an AAS (containing Submodels containing File Submodel Elements) via the BaSyx Web UI and subsequently deleting it all, the documents remain in the MongoDB fs.files and fs.chunks collections. The AAS is correctly removed from the registry and repository, but the corresponding files are not cleaned up.
To Reproduce
- Start BaSyx Java off-the-shelf components using Docker Compose with a MongoDB backend and Port-Mapping
'27017:27017'
- Open the BaSyx Web UI
- Upload an AAS (.aasx package) with a Submodel that contains some files in Submodel Element
File
- Delete the same AAS and all of its Submodels via the Web UI
- Connect to the MongoDB instance (e.g. using MongoDB Compass)
- Inspect the
fs.files and fs.chunks collections in aas-env database
Expected behavior
After deleting an AAS and its Submodels, all associated data should be removed from MongoDB.
Description
When uploading an AAS (containing Submodels containing
FileSubmodel Elements) via the BaSyx Web UI and subsequently deleting it all, the documents remain in the MongoDBfs.filesandfs.chunkscollections. The AAS is correctly removed from the registry and repository, but the corresponding files are not cleaned up.To Reproduce
'27017:27017'Filefs.filesandfs.chunkscollections inaas-envdatabaseExpected behavior
After deleting an AAS and its Submodels, all associated data should be removed from MongoDB.