Dwrite commented on PR #4339:
URL: https://github.com/apache/calcite/pull/4339#issuecomment-3111833608
java.lang.RuntimeException: Error while parsing query: values (2 ^^ 3)
at
org.apache.calcite.sql.test.AbstractSqlTester.parseAndValidate(AbstractSqlTester.java:158)
at
org.apache.calcite.sql.test.AbstractSqlTester.check(AbstractSqlTester.java:240)
at org.apache.calcite.sql.test.SqlTester.check(SqlTester.java:158)
at
org.apache.calcite.test.SqlOperatorFixtureImpl.lambda$checkScalar$2(SqlOperatorFixtureImpl.java:240)
at
org.apache.calcite.sql.test.AbstractSqlTester.forEachQuery(AbstractSqlTester.java:454)
at
org.apache.calcite.test.SqlOperatorFixtureImpl.checkScalar(SqlOperatorFixtureImpl.java:239)
at
org.apache.calcite.sql.test.SqlOperatorFixture.checkScalar(SqlOperatorFixture.java:232)
at
org.apache.calcite.test.SqlOperatorTest.testBitXorOperatorScalarFunc(SqlOperatorTest.java:16468)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
....
Caused by: org.apache.calcite.sql.parser.SqlParseException: Encountered "^
^" at line 1, column 11.
Hi,
Just to clarify, Quidem replaces ^^ with a single caret ^ before executing
the tests. So in test inputs, we need to write ^^ to represent an actual caret.
The issue is that this replacement happens multiple times during test
processing, which means the caret count reduces each time the test runs. This
breaks idempotency, because the SQL changes after the first run, causing
failures or unexpected behavior on subsequent runs.
That’s why relying solely on doubling carets (^^) isn’t an ideal solution.
We need a way to handle single carets properly to ensure consistent behavior
across multiple executions.
Thanks for understanding!
--
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]
