range partition key name prefix with '#' issue in 3.3.0rc2

[sanikoyes]

In current master(3.3.0rc2) version, when a field starting with the # character is used as the key of a range partition expression, and there is a field with the same name that does not start with # in the table, the system will recognize that the field that does not start with # is used as the partition field.

Steps to reproduce the behavior (Required)

1. CREATE TABLE

   CREATE TABLE site_access1 (
   `#event_day` DATETIME NOT NULL,
   site_id INT DEFAULT '10',
   city_code VARCHAR(100),
   user_name VARCHAR(32) DEFAULT '',
   event_day DATETIME NOT NULL,
   pv BIGINT DEFAULT '0'
   )
   DUPLICATE KEY(`#event_day`, site_id, city_code, user_name)
   PARTITION BY date_trunc('day', `#event_day`)
   DISTRIBUTED BY HASH(`#event_day`, site_id);

2. SHOW CREATE TABLE

• In starrocks version 3.2.6-2585333

  StarRocks > show create table site_access1\G
  *************************** 1. row ***************************
     Table: site_access1
  Create Table: CREATE TABLE `site_access1` (
  ...
  ) ENGINE=OLAP 
  ...
  PARTITION BY date_trunc('day', #event_day)
  ...

• In starrocks version 3.3.0-rc2 (master version)

  StarRocks > show create table site_access1\G
  *************************** 1. row ***************************
     Table: site_access1
  Create Table: CREATE TABLE `site_access1` (
  ...
  ) ENGINE=OLAP 
  ...
  PARTITION BY date_trunc('day', event_day)
  ...

Partition range key #event_day -> event_day

Expected behavior (Required)

PARTITION BY date_trunc('day', #event_day)

Real behavior (Required)

PARTITION BY date_trunc('day', event_day)

StarRocks version (Required)

• You can get the StarRocks version by executing SQL select current_version()

[xiangguangyxg]

Fixed in 3.3.0