@Tim Armstrong I actually verified by running the bin/parse-thrift-profile.py on the profile that was generated by Impala 3.2 and I don't see the exec_summary (the top level struct) being filled, where as the string ExecSummary is filled perfectly:     ... ... ExecSummary': '\nOperator #Hosts Avg Time Max Time #Rows Est. #Rows Peak Mem Est. Peak Mem Detail \n--------------------------------------------------------------------------------------------------------------------------------------------------------------------\nF06:ROOT 1 0.000ns 0.000ns 0 0 \n17:MERGING-EXCHANGE 1 0.000ns 0.000ns 100 100 16.00 KB 16.00 KB UNPARTITIONED \nF04:EXCHANGE SENDER 1 0.000ns 0.000ns 2.09 KB 0 \n10:TOP-N 1 1.000ms 1.000ms 100 100 60.00 KB 5.66 KB \n09:HASH JOIN 1 1.000ms 1.000ms 26.29K 5.76M 12.05 MB 8.50 MB INNER JOIN, BROADCAST \n|--16:EXCHANGE 1 0.000ns 0.000ns 144.00K 144.00K 9.88 MB 4.15 MB BROADCAST \n| F05:EXCHANGE SENDER 1 36.000ms 36.000ms 3.88 KB 0 \n| 08:SCAN HDFS 1 135.001ms 135.001ms 144.00K 144.00K 11.56 MB 48.00 MB tpcds_bin_partitioned_orc_2.customer \n15:AGGREGATE 1 8.000ms 8.000ms 26.29K 5.76M 34.05 MB 128.00 MB FINALIZE \n14:EXCHANGE 1 0.000ns 0.000ns 26.29K 5.76M 200.00 KB 10.05 MB HASH(ss_ticket_number,ss_customer_sk,ss_addr_sk,store.s_city) \nF00:EXCHANGE SENDER 1 8.000ms 8.000ms 2.41 KB 0 \n07:AGGREGATE 1 22.000ms 22.000ms 26.29K 5.76M 34.34 MB 128.00 MB STREAMING \n06:HASH JOIN 1 14.000ms 14.000ms 280.27K 5.76M 2.18 MB 1.94 MB INNER JOIN, BROADCAST \n|--13:EXCHANGE 1 0.000ns 0.000ns 5.04K 720 184.00 KB 25.31 KB BROADCAST \n| F03:EXCHANGE SENDER 1 1.000ms 1.000ms 7.52 KB 0 \n| 03:SCAN HDFS 1 24.000ms 24.000ms 5.04K 720 877.14 KB 48.00 MB tpcds_bin_partitioned_orc_2.household_demographics \n05:HASH JOIN 1 6.000ms 6.000ms 280.27K 5.76M 2.11 MB 1.94 MB INNER JOIN, BROADCAST \n|--12:EXCHANGE 1 0.000ns 0.000ns 21 2 16.00 KB 16.00 KB BROADCAST \n| F02:EXCHANGE SENDER 1 0.000ns 0.000ns 5.12 KB 0 \n| 02:SCAN HDFS 1 31.000ms 31.000ms 21 2 712.07 KB 48.00 MB tpcds_bin_partitioned_orc_2.store \n04:HASH JOIN 1 9.000ms 9.000ms 280.27K 5.76M 2.03 MB 1.94 MB INNER JOIN, BROADCAST \n|--11:EXCHANGE 1 0.000ns 0.000ns 156 7.30K 16.00 KB 134.14 KB BROADCAST \n| F01:EXCHANGE SENDER 1 0.000ns 0.000ns 7.52 KB 0 \n| 01:SCAN HDFS 1 41.000ms 41.000ms 156 7.30K 969.86 KB 48.00 MB tpcds_bin_partitioned_orc_2.date_dim \n00:SCAN HDFS 1 1s109ms 1s109ms 280.27K 5.76M 34.90 MB 64.00 MB tpcds_bin_partitioned_orc_2.store_sales' ... ... exec_summary=TExecSummary(status=None, is_queued=None, queued_reason=None, error_logs=None, state=0, progress=None, nodes=None, exch_to_sender_map=None     ... View more

So, would Impala by default generate the full profile tree (with all the fields)? ... View more

OK. Are there any impala options to be set in order to get the full profile tree? I mean does the profile creation always create all the fields unconditionally? ... View more

I am checking for a completed query which is a select statement and I see that the Query Summary (which has the execSummary string) is filled, but not the above exec_summary struct. ... View more