**Findings after Code Inspection -** Looking at the code, having back-ticks within SchemaPath is not necessary (this is my understanding) - Back-ticks are useful in the context of a compound name such as T.`column.with.a.dot`.another_column - As soon as individual parts are parsed then the back-ticks can be omitted
Then why Aggregator was able to handle columns having back-ticks (and whatever I could throw at it ) - I found logic to strip the extra back-ticks within the aggregator code **Suggested Fix -** - Stripping the back-tick from the MaterializedField names within Parquet seems to fix the HashJoin issue - The Aggregator didn't seem bothered by this change either [ Full content available at: https://github.com/apache/drill/pull/1445 ] This message was relayed via gitbox.apache.org for [email protected]
