Reduce database bloat by filtering CA configuration from scheduled properties

Description

The 4.x Asset Manager adds all the CA configuration properties to the properties of a scheduled event.

For example:

mysql> select mediapackage_id, count(mediapackage_id) from mh_assets_properties where namespace='org.opencastproject.scheduler.ca.configuration' group by mediapackage_id;

For our Galicaster 2.x CAs, there are 41 to 44 properties recorded for each scheduled event. So for 5000 scheduled events, mh_assets_properties could have an extra 200,000 rows.

This is not very helpful, as there doesn't seem to be any value in doing so.

Activity

Show:
Stephen Marquard
February 19, 2019, 8:24 AM

This is fixed by the new scheduler code in Opencast 7

Stephen Marquard
January 19, 2018, 6:33 PM

A lot of what Galicaster sends through in the way of config properties is not necessary:

https://github.com/teltek/Galicaster/issues/572

but capture.device.* info is useful for Opencast to have available (for example for monitoring scripts, dashboards, etc.) but is not useful on a per-event basis.

Fixed and reviewed

Assignee

Unassigned

Reporter

Stephen Marquard