timbytimmy opened a new issue, #16406: URL: https://github.com/apache/iotdb/issues/16406
### Search before asking - [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar. ### Version version 2.0.5 (Build: 0917050) ### Describe the bug and provide the minimal reproduce step DELETE DATABASE root.db1; CREATE DATABASE root.db1; CREATE TIMESERIES root.db1.t2.c0 INT64; CREATE TIMESERIES root.db1.t2.c1 INT64; CREATE TIMESERIES root.db1.t2.c2 INT32; INSERT INTO root.db1.t2(timestamp, c0, c1, c2) VALUES (1641024000000, 123, 1, 456); #query 1 SELECT c2 AS ref0, c0 AS ref1 FROM root.db1.t2 WHERE c1 = 1 OR 1=0; #query 2 SELECT c2 AS ref0, c0 AS ref1 FROM root.db1.t2 WHERE c1 = 1 OR 1!=0; #query 3 SELECT c2 AS ref0, c0 AS ref1 FROM root.db1.t2 WHERE c1 = 1 AND 1=1; ### What did you expect to see? query 1 : return 1 result query2 : return 1 result query3 : return 1 result ### What did you see instead? query 1 : return 1 result query2 : return 1 result query3 : 305 INTERNAL_SERVER_ERROR ### Anything else? dear IoTDB team, I found out adding a logically neutral constant to a WHERE clause using AND 1 = 1 causes INTERNAL_SERVER_ERROR (305), while the equivalent OR 1=1 does not. This looks like the crash is tied to neutral conjuncts in AND ### Are you willing to submit a PR? - [ ] 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]
