[Doris on ES] unix_timestamp(date_format(now(), '%Y-%m-%d')) not push down

[BabySid]

Describe the bug

I found a slow query:

select k1 from mytable where Updatetime < unix_timestamp(date_format(now(), '%Y-%m-%d')) ;

It costs more than 5s.

The log in be.INFO is

{"query":{"match_all":{}},"stored_fields":"_none_","docvalue_fields":["k1","UpdateTime"],"sort":["_doc"],"size":4096}

i used another sql with the same meaning:

select k1 from mytable where Updatetime < 1589212800;

it costs less then 1s.

The log in be.INFO is

 {"query":{"bool":{"filter":[{"bool":{"should":[{"range":{"UpdateTime":{"lt":"1589212800"}}}]}}]}},"stored_fields":"_none_","docvalue_fields":["k1","UpdateTime"],"sort":["_doc"],"size":4096}

I suspect that these basic functions (e.g. unix_timestamp(date_format(now(), '%Y-%m-%d'))) are not precomputed.

Version: Master

[wuyunfeng]

emm...

[wuyunfeng]

@blackfox1983
I think maybe the reason maybe is Data-Type is different with unix_timestamp(date_format(now(), '%Y-%m-%d')),
I just create a table:

CREATE EXTERNAL TABLE `fucntion_push` (
  `k1` bigint COMMENT "",
   `k2`  date COMMENT ""
) ENGINE=ELASTICSEARCH

create a mapped index in es:

PUT function_push
{
   "settings": {
      "index": {
         "number_of_shards": "1",
         "number_of_replicas": "0"
      }
   },
   "mappings": {
      "doc": {
         "properties": {
            "k1": {
               "type": "long"
            },
            "k2": {
               "type": "date"
            }
         }
      }
   }
}

SQL :

explain select * from fucntion_push where k1 > unix_timestamp(date_format(now(), '%Y-%m-%d'));

explain by Doris:

As we can see date_format(now(), '%Y-%m-%d') can be pre-computed by Doris FE, but because k1 datatype is different with the returned type unix_timestamp, all these two Expr become CastExpr.

another SQL：

explain select * from fucntion_push where k2 > date_format(now(), '%Y-%m-%d');

explain by Doris:

[wuyunfeng]

BTW, it seems Doris can not rewrite nested function: