This type of query is certainly supported. A few things to check to see if Drill might be encountering a bug: 1. Does the EXPLAIN plan for <query> complete ? If not, you should file a JIRA and provide some details about the tables. 2. If 1 completes, you should check how big are the tables and start adding one join at a time to determine at what point does the query not return in a reasonable period of time. Can you identify one particular join that is causing the problem or is it just the total number of joins that causes the problem. 3. If the query seems to be hanging, someone would have to examine the query profile (from the web UI), and/or jstack and/or drillbit.log
On Fri, Apr 29, 2016 at 6:21 AM, <[email protected]> wrote: > Hi , > > We are trying to execute below query on apache drill and not getting any > result. If we remove some of joins from query then we are good to get the > result. > If is there any limitation of join and where clause in side Apache drill > ,Please provide your input or make us correct to how to use Join and > Where clause inside Apace drill > > > > select activity.week, sum(activity.grossadd_inwards),sum(activity.cltv) > from > dfs.`/parquet-location/FA1D24E2-7B9B-407B-A18B-839C84B6E9B3-WL_Online_Search_Snapshot_Data.parquet` > as activity join(select product from > product_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view0 on activity.product=view0.product JOIN(select > halo_indicator_product from > halo_indicator_product_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view1 on activity.halo_indicator_product=view1.halo_indicator_product > JOIN(select subdma from > subdma_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view2 on activity.subdma=view2.subdma JOIN( select week from > week_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data ) > as view3 on activity.week=view3.week JOIN(select estimated_measure_type > from > estimated_measure_type_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view4 on activity.estimated_measure_type=view4.estimated_measure_type > JOIN(select snapshot_id from > snapshot_id_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view5 on activity.snapshot_id=view5.snapshot_id JOIN (select > primary_message from > primary_message_FA1D24E2_7B9B_407B_A18B_839C84B6E9B3_WL_Online_Search_Snapshot_Data) > as view6 on activity.primary_message=view6.primary_message group by > activity.week > > Please do let us know if you require any more information from our side. > > Regards, > Maneesh > > ________________________________ > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise confidential information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the e-mail by you is prohibited. Where allowed > by local law, electronic communications with Accenture and its affiliates, > including e-mail and instant messaging (including content), may be scanned > by our systems for the purposes of information security and assessment of > internal compliance with Accenture policy. > > ______________________________________________________________________________________ > > www.accenture.com >
