Remove all traces of MongoDB from dependencies, code and documentation
After successfull migration to version 2.0 MongoDB is no longer necessary. Wait for reasonable amount of time to let users perform the migration.
Removed all mentions of MongoDB from documentation, added deprecation warnings to code libraries.
The only places in documentation where MongoDB mentions were kept are for obvious reasons installation and migration pages. (Redmine issue: #4225)
This commit removes support for MongoDB migrations to PostgreSQL.
After this all code related to MongoDB is gone and database migration from MongoDB to PostgreSQL is no longer possible. I have kept the documentation page about migration for now, so that the users can still at least find the information. (Redmine issue: #4225)
Removed more unnecessary code related to MongoDB.
The methods removed in this commit took care of escaping '.' characters in disctionary keys, because in MongoDB it was reserved character. (Redmine issue: #4225)
Canceled explicit sorting of IP addresses to keep the original order.
IDEA event objects contain utility method for retrieving all Source/Target IP addresses. I have reverted the changes from previous commit to keep the addresses in original order. Minor coding style improvements. (Redmine issue: #4225)
#1 Updated by Radko Krkoš about 1 year ago
MongoDB daemon is still running on new/upgraded installations. Based on VC discussion, it could be safely stopped and disabled, as was done on
mentat-hub. If this issue is postponed, consider performing these steps during installation - MongoDB is required only for installation, after data migration, it has no purpose.
#3 Updated by Jan Mach about 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
I have removed all traces of MongoDB from codebase. I have kept the documentation page about migration for now, so that users can at least find information. I think that the documentation page should not prevent from closing this issue.
I will deploy the updated codebase to development server and close this issue after verification that everything is working in order.