Loading...
Loading...
Hi all ! I'm currently using MongoDB from EPEL7 repos (version 2.6.5) and on RHEL7 (replica set deployment). I've changed the default configuration file to switch to the YAML format and set the "javascriptEnabled" to false, which seems to have no effect. From mongod logs, I checked that parameter is read : 2015-04-01T15:57:42.800+0200 [initandlisten] options: { command: [ "run" ], config: "/etc/mongodb.conf", net: { bindIp: "10.33.48.29,127.0.0.1", port: 27017 }, processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid" }, replication: { oplogSizeMB: 10240, replSetName: "rs0" }, security: { authorization: "enabled", javascriptEnabled: false, keyFile: "/var/lib/mongodb/mongod-key" }, storage: { dbPath: "/var/lib/mongodb", directoryPerDB: true, journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongodb.log", quiet: true } } Then, we tried this JS function : db.client.aggregate({$group: { _id : '$name', total : { $sum : 1 } } }) and got a result.
sboulkour commented on Tue, 14 Apr 2015 16:00:59 +0000: My bad, we used that group() function and got the expected result. Sorry about that :/ ramon.fernandez commented on Tue, 14 Apr 2015 15:48:42 +0000: sboulkour, the operation you posted is not db.collection.group() (which requires JavaScript) but db.collection.aggregate() with a $group pipeline stage, which does not require JavaScript. Regards, Ramón.
Set javascriptEnabled to false, restart all servers in replica set, and try to execute a JS job.
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.