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

Query profiles should clearly indicate storage layer(s) used

    XMLWordPrintableJSON

Details

    Description

      Currently, the query profile doesn't have the location of tables and partitions, which makes it hard to figure out what storage layer a table/partition that was queried was on.

      As we're seeing more users run Impala workloads against cloud based storage like S3 and ADLS, we should have the query profiles show this information.

      Attachments

        Issue Links

          Blocked

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-10087 IMPALA-6050 causes alluxio not to be supported

          • Major - Major loss of function.
          • Resolved
          breaks

          Test - A new unit, integration or system test. IMPALA-8415 test_corrupt_stats exhaustive test failed

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          is duplicated by

          Task - A task that needs to be done. IMPALA-3559 Explain plan and profiles reference HDFS while query is running entirely against S3

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue IMPALA-7097 Print EC info in the query plan and profile

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              stakiar Sahil Takiar
              sailesh Sailesh Mukil
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: