LingweiKuang opened a new issue, #14140: URL: https://github.com/apache/iotdb/issues/14140
### Search before asking - [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar. ### Version version 1.3.2 (Build: aa0ff4a) ### Describe the bug and provide the minimal reproduce step ``` DROP DATABASE root.db0 CREATE DATABASE root.db0 CREATE TIMESERIES root.db0.t1 WITH datatype=BOOLEAN; insert into root.db0(timestamp,t1) values(1724497540136, true) insert into root.db0(timestamp,t1) values(1724497540137, false) # query 1 success SELECT t1 FROM root.db0 WHERE !FALSE # query 2 success SELECT t1 FROM root.db0 WHERE CAST(t1 as BOOLEAN) # query 3 error SELECT t1 FROM root.db0 WHERE !CAST(t1 as BOOLEAN) ``` ### What did you expect to see? Query 1 returned result set: true and false Query 2 returned result set: true Query 3 returned result set: false ### What did you see instead? Query 1 returned result set: true and false Query 2 returned result set: true Query 3 reported an error: Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: This predicate contains a not! Did you forget to run this predicate through PredicateRemoveNotRewriter? ### Anything else? Dear IoTDB team, The BOOLEAN value returned by CAST(t1 AS BOOLEAN) should be able to work with the NOT operator. This might be a bug. ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
