Hi guys, I raised:
https://issues.apache.org/jira/browse/DRILL-2732 I'd be keen to get stuck in and implement a patch for this, but I was hoping someone might be able to point me in the right direction. The behaviour seems extremely strange that a field name could affect a query plan. Ultimately, the Mongo filter pushdown optimization rule (which is the real reason this is causing me pain) should handle cases where there is a project between the scan and filter, but I can't work out why this would be happening. I'll keep researching the codebase, but if someone knows where I should look, that would really help!
