Skip to content

Allow database used for MUC MAM to be configurable #146

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.

Sign up for GitHub

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

Jump to bottom
Closed
guusdk opened this issue Dec 11, 2020 · 1 comment
Closed

Allow database used for MUC MAM to be configurable #146

guusdk opened this issue Dec 11, 2020 · 1 comment

Comments

@guusdk
Copy link
Member

guusdk commented Dec 11, 2020

Openfire, as well as the Monitoring plugin, provides a database table where MUC messages are stored (this does not hold true for one-on-one messages, which are only stored in a database table provided by the Monitoring plugin).

The content of both tables is roughly equivalent, but is different in specific details (eg: with #133, PMs will only be available in the database-table provided by the Monitoring plugin).

Version 2.2.0 of the Monitoring plugin will switch from using the Openfire-provided table to the one provided by the Monitoring plugin. However, for specific use cases, it could be desirable to keep using the Openfire-provided table.

A configurable property should be introduced that can be used to define what table is to be used.
guusdk added a commit to guusdk/openfire-monitoring-plugin that referenced this issue Dec 11, 2020
@guusdk
fixes igniterealtime#146: Add option to choose between database used …
454b2d4 
…for MUC archive

The archived MUC messages are persisted to the database more than once: Openfire stores them in ofMucConversationLog, the Monitoring plugin in ofMessageArchive.

This commit introduces a configuration option to switch between the two: conversation.database.use-openfire-tables

The default for this new option is to use the database table provided by the Monitoring plugin, which is a change from the behavior prior to this commit.
@guusdk
Copy link
Member Author

guusdk commented Dec 11, 2020

The property that will be used for this is conversation.database.use-openfire-tables - it takes a boolean value, and defaults to false

guusdk added a commit to guusdk/openfire-monitoring-plugin that referenced this issue Dec 16, 2020
@guusdk
addendum to igniterealtime#146: Use correct database table for lookups
fc2a0d0 
With the changes for igniterealtime#146, the database table used for MUC queries is configurable. This commit makes sure that the correct table is used for lookups of some metadata (SSID, first and last date).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@guusdk