Skip to content

json_extract using '0' report error #6388

@aytrack

Description

@aytrack

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

drop table if exists t;
create table t (a int, b json);
alter table t set tiflash replica 1;
insert into t values (1, '-1E-36181012216111515851075235238'),(2, '1E-36181012216111515851075235238'), (3, '1E-325'), (4, '1E-324'), (5, '1E-323'), (6, '1E+308');
SELECT JSON_EXTRACT(b, '$') from t;

2. What did you expect to see? (Required)

query success and got correct result.

+----------------------+
| JSON_EXTRACT(b, '$') |
+----------------------+
| -0                   |
| 0                    |
| 0                    |
| 0                    |
| 1e-323               |
| 1e+308               |
+----------------------+

3. What did you see instead (Required)

[11:31:04]MySQL root:test> SELECT JSON_EXTRACT(b, '$') from t;
(1105, 'other error for mpp stream: From MPP<query:437722563221651457,task:1>: Code: 49, e.displayText() = DB::Exception: Check first_path_ref failed, e.what() = DB::Exception,')

4. What is your TiFlash version? (Required)

[11:31:30]MySQL root:test> select * from information_schema.cluster_info;
+---------+--------------------+--------------------+-------------------------------+------------------------------------------+---------------------------+--------------------+-----------+
| TYPE    | INSTANCE           | STATUS_ADDRESS     | VERSION                       | GIT_HASH                                 | START_TIME                | UPTIME             | SERVER_ID |
+---------+--------------------+--------------------+-------------------------------+------------------------------------------+---------------------------+--------------------+-----------+
| tidb    | 172.16.5.130:4000  | 172.16.5.130:21080 | 6.5.0-alpha                   | d0b72a2cc79bc8568935e30d49d1f269af1ce0ee | 2022-11-30T10:21:19+08:00 | 1h10m11.862807513s | 1385189   |
| pd      | 172.16.5.130:12379 | 172.16.5.130:12379 | 6.5.0-alpha                   | 2a4f9a0dd14c0c9a1fc211b3a84468c635b277a8 | 2022-11-30T10:11:46+08:00 | 1h19m44.862816068s | 0         |
| tikv    | 172.16.5.130:21161 | 172.16.5.130:21181 | 6.5.0-alpha                   | bfe29655a2a1634c268a7fb3986892be7dc1f305 | 2022-11-30T10:11:50+08:00 | 1h19m40.862817942s | 0         |
| tikv    | 172.16.5.130:21163 | 172.16.5.130:21183 | 6.5.0-alpha                   | bfe29655a2a1634c268a7fb3986892be7dc1f305 | 2022-11-30T10:11:50+08:00 | 1h19m40.862819573s | 0         |
| tikv    | 172.16.5.130:21162 | 172.16.5.130:21182 | 6.5.0-alpha                   | bfe29655a2a1634c268a7fb3986892be7dc1f305 | 2022-11-30T10:11:50+08:00 | 1h19m40.8628252s   | 0         |
| tiflash | 172.16.5.130:3930  | 172.16.5.130:20292 | 6.5.0-alpha-52-ga38ab58-dirty | a38ab58b656a8bbdfb01a1ff9e0aa19f361f21ef | 2022-11-30T10:21:57+08:00 | 1h9m33.862826848s  | 0         |
+---------+--------------------+--------------------+-------------------------------+------------------------------------------+---------------------------+--------------------+--------

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions