[ https://issues.apache.org/jira/browse/DRILL-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Victoria Markman updated DRILL-2732: ------------------------------------ Fix Version/s: (was: 1.0.0) 1.1.0 > Different logical plan based on field names > ------------------------------------------- > > Key: DRILL-2732 > URL: https://issues.apache.org/jira/browse/DRILL-2732 > Project: Apache Drill > Issue Type: Bug > Components: Query Planning & Optimization > Affects Versions: 0.8.0 > Reporter: Adam Gilmore > Assignee: Jinfeng Ni > Fix For: 1.1.0 > > > The following two queries produce different logical plans: > {code} > select count(*) from cp.`employee.json` where mytestFieldNum = 4 and > myOtherLongIdString = '12345' > {code} > {code} > select count(*) from cp.`employee.json` where my_testFieldNum = 4 and > my_OtherLongIdString = '12345' > {code} > The latter adds a project step to the logical plan. The ramifications of > this means that, for example, the Mongo storage provider will not push down > filters because it's matching on a scan/filter. > It has nothing to do with the underscore - in fact, it seems if you > substitute the underscore with a variety of characters, it produces different > results. > It also seems to not be reliant on the length of the field names in question. > These two queries should really produce identical logical plans. -- This message was sent by Atlassian JIRA (v6.3.4#6332)