[DRILL-1685] MongoDB plugin - Drill not showing correct error when using the wrong MongoDB database

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: Future
• Component/s: Storage - MongoDB

Environment

Drill 0.6, MongoDB 2.6.5

• Assignee: Unassigned
• Reporter: Andries Engelbrecht
• Created: 11/Nov/14 19:06
• Updated: 26/Jan/15 22:47
• Resolved: 26/Jan/15 22:47

Description

When connecting to MongoDB with multiple databases and collections drill fails to recognize the use of unavailable tables/collections.

Example:
In the reviews database there are review, user, business collections/tables.
In the twitter database there is a tweets collection/table.

When connecting to the reviews database (use mongo.reviews and then incorrectly trying to access the tweets table in the twitter database sqlline returns the following error:

Query failed: Failure while setting up Foreman. Internal error: Error while applying rule DrillPushProjIntoScan, args [rel#5522:ProjectRel.NONE.ANY([]).[](child=rel#5521:Subset#0.ENUMERABLE.ANY([]).[],date=SUBSTRING($1, 1, 10)), rel#5510:EnumerableTableAccessRel.ENUMERABLE.ANY([]).[](table=[mongo, reviews, tweets])] [68adba1a-3f55-4f95-ad61-be3a7550a26d]

Instead of simply identifying that the tweets table/collection is not in the current database.

Issue Links

• duplicates: DRILL-1586 NPE when the collection being queried for does not exist in Mongo DB