Closed davidemarrone closed 3 months ago
Hi,
Yes, it's possible to configure different data-sources using different repositories and then configure actual repositories (in this case msgRepository
) to use mongodb implementation and point it to use mongo://…
data source.
There is no "migration" path available so you would have to manually move the messages from one database engine to the other.
yes I know that I have to migrate old data manually, but the table is simple so I do not see any problem, thanks
Hi, regarding this issue is tigase compatible also with https://aws.amazon.com/documentdb/ instead of MongoDB? Do you have already tested it? Or I need to check if all the operations used by tigase are supported by DocumentDb ?
Hi, here are the supported commands by DocumentDb: https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html
with low priority could you check if tigase is using only commands supported also by DocumentDb ? Thanks
The issue was migrated here: https://tigase.dev/tigase/_server/server-core/~issues/1472 and I commented it there
Isolating msg_history to mongoDB We are running our cluster on mysql, is it possible to "migrate" only the table msg_history from mysql to mongodb? Can we with config.tdsl change only the storage of offline messages from mysql to mongodb?
Details: