Re: [Question] Regarding the loading conflict between SqlStdOperatorTable and SqlLibraryOperators

Hello, I conducted debugging, and the result is as you said. I may need some time to think about how to modify this part of the code. Thank you very much for your suggestion. Best regards， Cancai Cai Benchao Li 于2024年3月11日周一 21:09写道： > I didn't go deep into CALCITE-6259, so I might not able to

Re: [Question] Regarding the loading conflict between SqlStdOperatorTable and SqlLibraryOperators

I didn't go deep into CALCITE-6259, so I might not able to give you the precise solution / code. Generally, you can add your operator table in front of the standard operator table, or just leave the standard operator table out, that would meet the requirement that you want to "override" a standard

Re: [Question] Regarding the loading conflict between SqlStdOperatorTable and SqlLibraryOperators

It seems like I can't find a suitable way to solve this problem, can you give me some suggestions? Best regards, Cancai Cai Benchao Li 于2024年3月5日周二 19:26写道： > It's not a class loading problem, it's an operator lookup mechanism, > which is a by design behavior, you can see details here[1]. If th

Re: [Question] Regarding the loading conflict between SqlStdOperatorTable and SqlLibraryOperators

It's not a class loading problem, it's an operator lookup mechanism, which is a by design behavior, you can see details here[1]. If there are multiple candidates in the result of operator lookup, the first one will be returned. [1] https://github.com/apache/calcite/blob/d64ee0037db7abacdfcd4e7740

[Question] Regarding the loading conflict between SqlStdOperatorTable and SqlLibraryOperators

Hello, everyone in the calcite community. I'm not sure if I should ask this question. In the process of fixing CALCITE-6259 , I found that I defined a log10_MS function in SqlLibraryOperators to simulate the behavior of the log function in mysql