Re: Drill Join query optimization

I'm not familiar with Mongo storage plugin. But looking at the code, seems there is a MongoPushDownFilterForScan rule, which should be able to push the filter ta.Id ='123' into TableA. If your query plan does not show this filter is pushed down into Mongo Scan operator, there might be a bug in

Re: Drill Join query optimization

What version of Drill are you on ? Can you please share the query plan for your query ? Please share the table definitions ? Is this a standalone setup or cluster of Drillbits ? On Fri, Nov 4, 2016 at 2:23 PM, wrote: > Hello, > > I am working on a proof of

Drill Join query optimization

Hello, I am working on a proof of concept to optimize the performance of the join queries executed through drill. The underlying storage is a NO-SQL based database - Mongo DB. The time it takes to return the result of the join query is very high (46 seconds). Upon further analysis, as per the