cjj2010 commented on PR #4667:
URL: https://github.com/apache/calcite/pull/4667#issuecomment-3616161810

   > Test failed.
   > 
   > ```
   > <html>
   > <body>
   > <!--StartFragment-->
   > > Task :babel:test
   > --
   >   |   |   | 2.5sec, org.apache.calcite.test.BabelTest > testLeftSemiJoin()
   >   |   |   | 2.6sec, org.apache.calcite.test.BabelTest > testLeftAntiJoin()
   >   |   |   | 2.6sec, org.apache.calcite.test.BabelTest > testFixtures()
   >   |   |   | 2.7sec, org.apache.calcite.test.BabelTest > testTimeFrames()
   >   |   |   | 4.4sec, org.apache.calcite.test.BabelQuidemTest > 
test(String)[1], [1] sql/dummy.iq
   >   |   |   | 5.8sec, org.apache.calcite.test.BabelTest > testDatePart()
   >   |   |   | 6.0sec, org.apache.calcite.test.BabelTest > testNullSafeEqual()
   >   |   |   | FAILURE   6.1sec, org.apache.calcite.test.BabelTest > 
testInfixCast()
   >   |   |   | java.lang.AssertionError: Invalid column type
   >   |   |   | Expected: is <2>
   >   |   |   | but: was <3>
   >   |   |   | at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
   >   |   |   | at 
org.apache.calcite.test.BabelTest.checkInfixCast(BabelTest.java:110)
   >   |   |   | at 
org.apache.calcite.test.BabelTest.testInfixCast(BabelTest.java:99)
   >   |   |   |  
   >   |   |   | FAILURE   6.1sec,    8 completed,   1 failed,   0 skipped, 
org.apache.calcite.test.BabelTest
   > 
   > <!--EndFragment-->
   > </body>
   > </html>
   > ```
   > 
   > You can run ./gradlew build to check it locally.
   
   I have read the code related to calciteJDBC and the current semantics of 
NUMERIC are equivalent to DECIMAL. However, currently in Java, NUMERIC and 
DECIMAL are different in sqlType. Therefore, you can refer to `sqlTypeNameTest` 
to add corresponding test cases. I have updated the code and the above is my 
personal opinion. Thank you for correcting me
   


-- 
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]

Reply via email to