You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2019/01/24 00:48:00 UTC

[jira] [Created] (IMPALA-8106) Cleanup of literal expression nodes

Paul Rogers created IMPALA-8106:
-----------------------------------

             Summary: Cleanup of literal expression nodes
                 Key: IMPALA-8106
                 URL: https://issues.apache.org/jira/browse/IMPALA-8106
             Project: IMPALA
          Issue Type: Improvement
          Components: Frontend
    Affects Versions: Impala 3.1.0
            Reporter: Paul Rogers
            Assignee: Paul Rogers


IMPALA-7902 cleaned up numeric literals to fix confusing cast logic, to avoid the need to analyze a literal, and so on. This ticket proposes to do the same for the other literal expressions which, as a whole, need less work than the numeric literal did. In particular:

* Remove the need to analyze any literal expression.
* Clean up the cumbersome way that code creates and analyzes literals.
* Much code uses an awkward sequence of steps to force a constant expression to s specific type. Streamline this code.
* The constant expression evaluator is confused about the return SQL type. Is it the type of the original expression (as often required in statements) or the simplest type (as required by catalog code such as partition keys.) Create two distinct methods: one for each case.

This work, in turn, is part of the ongoing effort to merge expression rewrites into a single-pass analysis phase in order to more cleanly introduce additional rewrite rules.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org