Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-1005

Plan Fragment numbering in the query profile does not patch EXPLAIN output

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 1.3.1
    • Impala 1.4
    • None
    • None

    Description

      here's an example:

      From Explain
      ------------------------------------------------------------
      F11:PLAN FRAGMENT [PARTITION=UNPARTITIONED]
      24:EXCHANGE [PARTITION=UNPARTITIONED]
      hosts=3 per-host-mem=unavailable
      tuple-ids=11 row-size=24B cardinality=120
      ------------------------------------------------------------

      Fragment 11 from the profile contains a scan.
      ------------------------------------------------------------
      Averaged Fragment 11:(Total: 632.876ms, non-child: 0ns, % non-child: 0.00%)
      DataStreamSender (dst_id=12):(Total: 9.154ms, non-child: 9.154ms, % non-child: 100.00%)

      • BytesSent: 855.64 KB
      • NetworkThroughput: 48.67 MB/sec
        MERGE_NODE (id=13):(Total: 623.441ms, non-child: 5.92ms, % non-child: 0.82%)
      • PeakMemoryUsage: 32.00 KB
        HDFS_SCAN_NODE (id=2):(Total: 618.349ms, non-child: 618.349ms, % non-child: 100.00%)

      Attachments

        Activity

          People

            alex.behm Alexander Behm
            alan@cloudera.com Alan Choi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: