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

["Jason Altekruse (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Altekruse resolved DRILL-1685.
------------------------------------
    Resolution: Fixed

> MongoDB plugin - Drill not showing correct error when using the wrong MongoDB database
> --------------------------------------------------------------------------------------
>
>                 Key: DRILL-1685
>                 URL: https://issues.apache.org/jira/browse/DRILL-1685
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - MongoDB
>    Affects Versions: 0.6.0
>         Environment: Drill 0.6, MongoDB 2.6.5
>            Reporter: Andries Engelbrecht
>            Priority: Minor
>             Fix For: Future
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)