-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprec/remove cassandra from mqtt #33
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overwall, great job here!
Since we have only one source of data now, Mongo DB, feature flags such as mongo.enabled
can be removed right away from everywhere.
Hey, the struct Message in model/message.go is a representation of the chat message stored in Cassandra, so it must be removed too. Along with this, some logic to convert a Message into a MessageV2 in mongoclient/get_messages.go that also be removed. |
607e9c4
to
ff161ec
Compare
|
ff161ec
to
3b637a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ship it 🚀
What?
To deprecate Cassandra infrastructure on MQTT History focusing on maintain only one database(MongoDB) on it.
What was changed?
In the list below you can check some of the modifications that were made to MQTT History for deprecating Cassandra: