Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D2C71016B for ; Sun, 4 Jan 2015 23:57:50 +0000 (UTC) Received: (qmail 14985 invoked by uid 500); 4 Jan 2015 23:57:51 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 14956 invoked by uid 500); 4 Jan 2015 23:57:51 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 14946 invoked by uid 99); 4 Jan 2015 23:57:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Jan 2015 23:57:51 +0000 Date: Sun, 4 Jan 2015 23:57:51 +0000 (UTC) From: "Jacques Nadeau (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-1685) MongoDB plugin - Drill not showing correct error when using the wrong MongoDB database MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau updated DRILL-1685: ---------------------------------- Fix Version/s: Future Priority: Minor (was: Major) > 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)