Hello Dipti,
You mention that "the same query works on some of the machines and is
impacting few other", could you provide more context? In which
environment(s) does it work? In which doesn't? In the environment(s) where
it fails, is this failure systematic or somewhat "random" (do you have
differe
Hi Dipti,
It seems to be caused by the mixed usage of data types. There is a
conflict between JavaType and SqlType. You can try to check whether
there is any problem with the mapping of SQL Server's metadata types
to Calcite's types. I recommend uniformly using Sqltype.
Yu Xu 于2025年2月27日周四 16:
On 2025/01/31 03:16:28 Dipti Kulkarni wrote:
> Hi Team,
>
> We have been using calcite in our product for a while and we are on 1.36
> version.
> Unfortunately, one of our queries that worked earlier have started failing
> and nothing changed on the calcite jars as we know of. Suddenly the
>
Hi Team,
We have been using calcite in our product for a while and we are on 1.36
version.
Unfortunately, one of our queries that worked earlier have started failing and
nothing changed on the calcite jars as we know of. Suddenly the comparison for
String to char is throwing a validation except
