[Bug] NOT LIKE parsing exception

[Wilson-BT]

Search before asking

• I had searched in the issues and found no similar issues.

Version

doris-2.0.3

What's Wrong?

When I execute this not like SQL, the Query in the parsing plan looks like this, causing the final query to be abnormal.

What You Expected?

Bug Fix

How to Reproduce?

No response

Anything Else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[WinkerDu]

Can you provide more info to reproduce this issue, like create table statement and query SQL

[yiguolei]

@Wilson-BT Need table schema and query sql information.

[Wilson-BT]

@Wilson-BT Need table schema and query sql information.

it`s a jdbc catalog table, table schema:

CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '自增主键',
  `full_name` varchar(150) NULL COMMENT '组织名称',
  `update_time` datetimev2(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '更新时间',
  `create_time` datetimev2(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间'
) ENGINE=JDBC_EXTERNAL_TABLE;

Sql ：

  select *
  from tidb_prod_tikv.ehr_sync.organization 
 where (full_name not like '%虚店%' )and (full_name not like '%直播%')

I think,you can create any jdbc catalog table, and use not like 'xxx' to reproduce this issue.

[WinkerDu]

I try to create jdbc catalog for external mysql table:

CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,
  `full_name` varchar(150) NULL,
  `update_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `create_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP
)

then execute query like:

explain select *
from mysql_jdbc_catalog.drp_db.organization 
 where (full_name not like '%虚店%' )and (full_name not like '%直播%');

I cannot reproduce this issue in Branch-2.0 branch for both Nereids planner and Old planner.
Nereids planner:

Old planner:

Maybe you can upgrade your Doris? @Wilson-BT
cc @yiguolei

[Wilson-BT]

I try to create jdbc catalog for external mysql table:

CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,
  `full_name` varchar(150) NULL,
  `update_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `create_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP
)

then execute query like:

explain select *
from mysql_jdbc_catalog.drp_db.organization 
 where (full_name not like '%虚店%' )and (full_name not like '%直播%');

I cannot reproduce this issue in Branch-2.0 branch for both Nereids planner and Old planner. Nereids planner: Old planner: Maybe you can upgrade your Doris? @Wilson-BT cc @yiguolei

OK. i have Already upgraded.The problem has been solved. Thank you for your attention.

[baofengzhouyu]

I try to create jdbc catalog for external mysql table:

CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,
  `full_name` varchar(150) NULL,
  `update_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `create_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP
)

then execute query like:

explain select *
from mysql_jdbc_catalog.drp_db.organization 
 where (full_name not like '%虚店%' )and (full_name not like '%直播%');

I cannot reproduce this issue in Branch-2.0 branch for both Nereids planner and Old planner. Nereids planner: Old planner: Maybe you can upgrade your Doris? @Wilson-BT cc @yiguolei

I have the same problem.
version: 2.0.3
Is there a bug in the latest version ?

[Wilson-BT]

I try to create jdbc catalog for external mysql table:

CREATE TABLE `organization` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,
  `full_name` varchar(150) NULL,
  `update_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `create_time` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP
)

then execute query like:

explain select *
from mysql_jdbc_catalog.drp_db.organization 
 where (full_name not like '%虚店%' )and (full_name not like '%直播%');

I cannot reproduce this issue in Branch-2.0 branch for both Nereids planner and Old planner. Nereids planner: Old planner: Maybe you can upgrade your Doris? @Wilson-BT cc @yiguolei

I have the same problem. version: 2.0.3 Is there a bug in the latest version ?

It may have been fixed in 2.0.4. Just wait and see