[jira] [Created] (DRILL-6996) Unauthorized command execution error received for Mongo
Kris Dalpiaz created DRILL-6996: --- Summary: Unauthorized command execution error received for Mongo Key: DRILL-6996 URL: https://issues.apache.org/jira/browse/DRILL-6996 Project: Apache Drill Issue Type: Bug Components: Storage - MongoDB Affects Versions: 1.15.0 Environment: Running in embedded mode. Storage: { "type": "mongo", "connection": "mongodb://[user]:[pass]@[host1]:[port1],[host2]:[port2],[host3]:[port3]/[db]?authMechanism=SCRAM-SHA-1&ssl=true&replicaSet=[set]", "enabled": true } Query: SELECT _id FROM [storage].[db].[collection]; Error: Error: SYSTEM ERROR: MongoCommandException: Command failed with error 13 (Unauthorized): 'not authorized on [db] to execute command \{ count: "[collection]", query: {} }' on server [host1]:[port1]. The full response is { "ok" : 0.0, "errmsg" : "not authorized on [db] to execute command \{ count: \"[collection]\", query: {} }", "code" : 13, "codeName" : "Unauthorized" } Successful Robo command: db.runCommand({ count: "[collection]", query: {} }) Reporter: Kris Dalpiaz We recently upgraded from 1.13 to 1.15 for the support of Decimal128 between Drill and some of our Mongo dbs. We are now receiving a MongoCommandException error when trying to query a Mongo db. No auth settings have been changed for the previously working login, and the same login is able to execute the command through Robo 3T. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6996) Unauthorized command execution error received for Mongo
[ https://issues.apache.org/jira/browse/DRILL-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kris Dalpiaz updated DRILL-6996: Description: We recently upgraded from 1.13 to 1.15 for the support of Decimal128 between Drill and some of our Mongo dbs. We are now receiving a MongoCommandException error when trying to query a Mongo db. No auth settings have been changed for the previously working login, and the same login is able to execute the command through Robo 3T. Running in embedded mode. Storage: { "type": "mongo", "connection": "mongodb://[user]:[pass]@[host1]:[port1],[host2]:[port2],[host3]:[port3]/[db]?authMechanism=SCRAM-SHA-1&ssl=true&replicaSet=[set]", "enabled": true } Query: SELECT _id FROM [storage].[db].[collection]; Error: Error: SYSTEM ERROR: MongoCommandException: Command failed with error 13 (Unauthorized): 'not authorized on [db] to execute command { count: "[collection]", query: {} }' on server [host1]:[port1]. The full response is { "ok" : 0.0, "errmsg" : "not authorized on [db] to execute command { count: \"[collection]\", query: {} }", "code" : 13, "codeName" : "Unauthorized" } Successful Robo command: db.runCommand({ count: "[collection]", query: {} }) was:We recently upgraded from 1.13 to 1.15 for the support of Decimal128 between Drill and some of our Mongo dbs. We are now receiving a MongoCommandException error when trying to query a Mongo db. No auth settings have been changed for the previously working login, and the same login is able to execute the command through Robo 3T. > Unauthorized command execution error received for Mongo > --- > > Key: DRILL-6996 > URL: https://issues.apache.org/jira/browse/DRILL-6996 > Project: Apache Drill > Issue Type: Bug > Components: Storage - MongoDB >Affects Versions: 1.15.0 >Reporter: Kris Dalpiaz >Priority: Major > > We recently upgraded from 1.13 to 1.15 for the support of Decimal128 between > Drill and some of our Mongo dbs. We are now receiving a MongoCommandException > error when trying to query a Mongo db. No auth settings have been changed for > the previously working login, and the same login is able to execute the > command through Robo 3T. > Running in embedded mode. > Storage: > { "type": "mongo", "connection": > "mongodb://[user]:[pass]@[host1]:[port1],[host2]:[port2],[host3]:[port3]/[db]?authMechanism=SCRAM-SHA-1&ssl=true&replicaSet=[set]", > "enabled": true } > Query: > SELECT _id FROM [storage].[db].[collection]; > Error: > Error: SYSTEM ERROR: MongoCommandException: Command failed with error 13 > (Unauthorized): 'not authorized on [db] to execute command { count: > "[collection]", query: {} }' on server [host1]:[port1]. The full response is > { "ok" : 0.0, "errmsg" : "not authorized on [db] to execute command { count: > \"[collection]\", query: {} }", "code" : 13, "codeName" : "Unauthorized" } > Successful Robo command: > db.runCommand({ > count: "[collection]", > query: {} > }) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6996) Unauthorized command execution error received for Mongo
[ https://issues.apache.org/jira/browse/DRILL-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kris Dalpiaz updated DRILL-6996: Environment: (was: Running in embedded mode. Storage: { "type": "mongo", "connection": "mongodb://[user]:[pass]@[host1]:[port1],[host2]:[port2],[host3]:[port3]/[db]?authMechanism=SCRAM-SHA-1&ssl=true&replicaSet=[set]", "enabled": true } Query: SELECT _id FROM [storage].[db].[collection]; Error: Error: SYSTEM ERROR: MongoCommandException: Command failed with error 13 (Unauthorized): 'not authorized on [db] to execute command \{ count: "[collection]", query: {} }' on server [host1]:[port1]. The full response is { "ok" : 0.0, "errmsg" : "not authorized on [db] to execute command \{ count: \"[collection]\", query: {} }", "code" : 13, "codeName" : "Unauthorized" } Successful Robo command: db.runCommand({ count: "[collection]", query: {} })) > Unauthorized command execution error received for Mongo > --- > > Key: DRILL-6996 > URL: https://issues.apache.org/jira/browse/DRILL-6996 > Project: Apache Drill > Issue Type: Bug > Components: Storage - MongoDB >Affects Versions: 1.15.0 >Reporter: Kris Dalpiaz >Priority: Major > > We recently upgraded from 1.13 to 1.15 for the support of Decimal128 between > Drill and some of our Mongo dbs. We are now receiving a MongoCommandException > error when trying to query a Mongo db. No auth settings have been changed for > the previously working login, and the same login is able to execute the > command through Robo 3T. -- This message was sent by Atlassian JIRA (v7.6.3#76005)