[DRILL-2732] Different logical plan based on field names

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.8.0
• Fix Version/s: Future
• Component/s: Query Planning & Optimization
• Assignee: Unassigned
• Reporter: Adam Gilmore
• Created: 09/Apr/15 03:49
• Updated: 01/Oct/15 16:37

Description

The following two queries produce different logical plans:

select count(*) from cp.`employee.json` where mytestFieldNum = 4 and myOtherLongIdString = '12345'

select count(*) from cp.`employee.json` where my_testFieldNum = 4 and my_OtherLongIdString = '12345'

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.