Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
See http://www.mongodb.org/display/DOCS/Capped+Collections for more informations.
Comment | File | Size | Author |
---|---|---|---|
#5 | mongodb_watchdog-capped-revised2a.patch | 2.95 KB | hurleyit |
#3 | mongodb_watchdog-capped-revised2.patch | 2.44 KB | hurleyit |
#2 | mongodb_watchdog-capped-revised.patch | 4.22 KB | hurleyit |
#1 | mongodb_watchdog-capped.patch | 4.22 KB | dawehner |
Comments
Comment #1
dawehnerHere is a initial version, it drops the current collection and create a new capped one
Comment #2
hurleyit CreditAttribution: hurleyit commentedI tried out this patch. And I think there are a few issues with it but I ran into two when testing this patch. The term 'mongo' is misspelled mondo in a function name, mondodb_watchdog_settings, in mongodb_watchdog.admin.inc, and in a reference to the function in mongodb_watchdog_menu in mongodb_watchdog.module. I am attaching a revised patch that uses the correct spelling of mongo.
The other issue is that part of the patch to mongodb_watchdog.info failed.
Other potential issues:
1. I'm not sure it's wise to create another settings page for the MongoDB settings. These settings should probably appear with the other MongoDB Watchdog settings on the page admin/config/development/logging.
2. There is already a cap setting for the size of the Watchdog log, with the number of entries. Do we need to use a separate variable that is Mongo specific?
3. The patch assumes one is in the mongodb/mongodb_watchdog directory. My understanding, possibly flawed, is that it should assume placement in the mongodb directory instead.
Comment #3
hurleyit CreditAttribution: hurleyit commentedI created a new patch that adds the form elements to the existing MongoDB Watchdog page instead of creating a new one. This way the form controls are all in one place instead of being spread out among different pages. It does not attempt to reconcile the issue of two controls for setting the number of lines to save.
Comment #4
hurleyit CreditAttribution: hurleyit commentedThere are some issues I'm still working out. Don't use my revised-2 patch for now.
Comment #5
hurleyit CreditAttribution: hurleyit commentedI prepended the mongodb watchdog callback to the submit array instead of adding it to the end. This allows us to check if the user changed the capped settings during this submit. If there is a better way of doing this, I am more than willing to revise.
Comment #6
crea CreditAttribution: crea commentedDoesn't apply to cache.
Comment #7
fgmNo longer applies (CVS format patch ?)
Comment #8
fgmNote that a different version supporting capped collections was committed by chx on 2011-04-24 with no issue#, and message "Watchdog cleanup. Use $natural, implement clean log."
So maybe this issue is now fixed. Anyone willing to review ?
Comment #10
chx CreditAttribution: chx commentedYes this is fixed.