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

Distinguish numeric types and show implicit cast in EXTENDED explain plans

    XMLWordPrintableJSON

Details

    Description

      In this plan, it wasn't clear that the constant in the predicate was being evaluated to a double. Then the lhs required an implicit cast, and the predicate couldn't be pushed to Kudu:

      [localhost:21000] > explain select * from functional_kudu.alltypestiny where bigint_col < 1000 / 100;
Query: explain select * from functional_kudu.alltypestiny where bigint_col < 1000 / 100
+---------------------------------------------+
| Explain String                              |
+---------------------------------------------+
| Per-Host Resource Reservation: Memory=0B    |
| Per-Host Resource Estimates: Memory=10.00MB |
| Codegen disabled by planner                 |
|                                             |
| PLAN-ROOT SINK                              |
| |                                           |
| 00:SCAN KUDU [functional_kudu.alltypestiny] |
|    predicates: bigint_col < 10              |
+---------------------------------------------+

      We should make it more clear by printing it in a way that makes it clear that it's being interpreted as a DOUBLE, e.g. by wrapping in a cast.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-7805 NumericLiteral toSql() should render zero as 0, not 0-E38, 0.000, etc.

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

          Activity

            People

              asherman Andrew Sherman
              mjacobs Matthew Jacobs
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: