Tao Yi created IOTDB-4319:
-----------------------------
Summary: 400 Error "no data type found for path" in having clause
when using upper case
Key: IOTDB-4319
URL: https://issues.apache.org/jira/browse/IOTDB-4319
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.14.0-SNAPSHOT
Environment: Windows 10
Reporter: Tao Yi
Attachments: err.txt, image-2022-09-03-12-42-36-314.png
I try some queries in IoTDB-0.14.0-SNAPSHOT client, but got unexpected error
only when I use an upper case aggregate function in having.
These are the queries I executed:
create timeseries root.sg1.d1.t1 with datatype=FLOAT, encoding=plain;
create timeseries root.sg1.d1.t2 with datatype=FLOAT, encoding=plain;
insert into root.sg1.d1(timestamp, t1, t2) values(1, 0, 1);
insert into root.sg1.d1(timestamp, t1, t2) values(2, -1, 2);
insert into root.sg1.d1(timestamp, t1, t2) values(3, -2, 3);
select last_value(t1) from root.sg1.d1 group by([1, 4), 2ms) having
last_value(t2) > 0
select last_value(t1) from root.sg1.d1 group by([1, 4), 2ms) having
LAST_VALUE(t2) > 0
select last_value(t2) from root.sg1.d1 group by([1, 4), 2ms) having
LAST_VALUE(t2) > 0
!image-2022-09-03-12-42-36-314.png|width=848,height=339!
>From the result, the only difference between the first and the second query is
>changing the aggregate function in having clause from lower case to upper
>case. But when I change the column in select clause into the same as the
>having clause (without changing the upper case), we can still get the result.
>So I think it should be a bug.
This is the error info in IoTDB-server. Full stacktrace is in the attachment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
