Limit Messages per Conversation #281
Comments
|
Just as explanation: The Smarti conversation was meant to represent a section within a communication channel. This lead to the decision to store the messages with the conversation. However when integrations do establish a 1:1 mapping between communication channels and Smarti conversations their is a risk that the amount of messages in those channels do overrun the storage limit of MongoDB. Depending on the goals future versions might change the storage model to directly represent Channels and their messages. With messages stored as single documents in an own collections. Conversations would than be an additional class that just refer their the channel and the messages they contain |
* The limit is enforced on 2 places
1. with the `ConversationRepoListener`: required when a Conversation with more as the maximum allowed number of conversations is directly added to the Repository
2. with a `$slice` command in the update of `appendMessage(..)` of the `ConversationRepository`
* The limit is configured by `smarti.storage.mongodb.maxConvMsg` the default is `5000`
* configuration changes are applied only on the next update to an conversation. This is sufficient as this limit is intended to prevent Mongo Documents getting over the limit of 16MByte
* Added a UnitTest for the MongoRepository that validates this feature. For testing the limit is set to `50` messages
|
The number of messages per conversation is configureable via |
ghost
removed
the
The current storage model of conversations require to limit the number of messages per conversation to ensure respecting the document size limit of MongoDB of 16 megabytes.
Assuming ~200 chars average per message and ~200 chars required for additional information a limit of 5000 messages seams to be a reasonable limit.
The text was updated successfully, but these errors were encountered: