Details
-
Improvement
-
Resolution: Done
-
Blocker - P1
-
None
-
Any OS, MongoDB 2.0 onwards
*Location*: http://docs.mongodb.org/ecosystem/tutorial/getting-started-with-hadoop/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36
*Referrer*: http://docs.mongodb.org/ecosystem/tools/hadoop/
*Screen Resolution*: 1600 x 900
*repo*: docs-ecosystem
*source*: tutorial/getting-started-with-hadoop
Any OS, MongoDB 2.0 onwards *Location*: http://docs.mongodb.org/ecosystem/tutorial/getting-started-with-hadoop/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36 *Referrer*: http://docs.mongodb.org/ecosystem/tools/hadoop/ *Screen Resolution*: 1600 x 900 *repo*: docs-ecosystem *source*: tutorial/getting-started-with-hadoop
Description
If authentication is turned on in MongoDB, the examples (and any use of the connector) will fail due to the connector trying to run the internal db command 'splitVector'. As a result, need to document that if using auth=true in MongoDB, need to ensure the user(s) for the source and target DBs for the MapReduce have the following role assigned: 'clusterManager'
eg. in mongo shell run:
use mongo_hadoop
db.updateUser( "reportsUser",
{
roles : [
,
{ role : "clusterManager", db : "admin" } ]
}
)
If this is not set, when a connector job is run, it fails with an access control exception.