You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug and provide the minimal reproduce step
DROP DATABASE root.db0
CREATE DATABASE root.db0
CREATE TIMESERIES root.db0.t1 WITH datatype=DOUBLE compressor=GZIP 'MAX_POINT_NUMBER'='8';
INSERT INTO root.db0(timestamp, t1) VALUES (1676586471999, 0.1);
INSERT INTO root.db0(t1) VALUES (0.2);
# query 1 success
SELECT t1 FROM root.db0 WHERE t1 BETWEEN (0) AND (100.0)
# query 2 error
SELECT t1 FROM root.db0 WHERE 1 BETWEEN (t1) AND (100.0)
What did you expect to see?
Query 1 returned result set: 0.1 and 0.2
Query 2 returned result set: 0.1 and 0.2
What did you see instead?
Query 1 returned result set: 0.01 and 0.02
Query 2 reported an internal error: Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "SELECT t1 FROM root.db0 WHERE 1 BETWEEN (t1) AND (100.0)". executeStatement failed. java.lang.Long cannot be cast to java.lang.Double
Anything else?
Dear IoTDB team, I think this might be a bug. If this functionality is not supported, should relevant information be returned to inform the user of the error reason, instead of a 305 internal error?
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Version
version 1.3.3 (Build: ad95a7e)
Describe the bug and provide the minimal reproduce step
What did you expect to see?
Query 1 returned result set: 0.1 and 0.2
Query 2 returned result set: 0.1 and 0.2
What did you see instead?
Query 1 returned result set: 0.01 and 0.02
Query 2 reported an internal error: Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "SELECT t1 FROM root.db0 WHERE 1 BETWEEN (t1) AND (100.0)". executeStatement failed. java.lang.Long cannot be cast to java.lang.Double
Anything else?
Dear IoTDB team, I think this might be a bug. If this functionality is not supported, should relevant information be returned to inform the user of the error reason, instead of a 305 internal error?
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: