Re: Is it posible to change synthetic input names ($0, $1, etc) in explain plans?

Thanks for your fast response. I've created https://issues.apache.org/jira/browse/CALCITE-6394 to discuss about that.

Is it posible to change synthetic input names ($0, $1, etc) in explain plans?

Hi community, I'm trying to improve explain plans in Apache Pinot and one of the main complaints of our customers is how difficult it is to read the explain plans having to transform the synthetic input names into the corresponding logical field. Is there a way to improve that? Ideally these

Re: Remove a specific type coersion rule

see that > https://issues.apache.org/jira/browse/CALCITE-3550 was trying to provide > a way for people to change the coercion rules. Does that solution meet your > needs? > > Julian > > > > > On Feb 22, 2024, at 6:59 AM, Gonzalo Ortiz Jaureguizar < > golthir...@gmail.co

Remove a specific type coersion rule

Hello there, In the context of https://issues.apache.org/jira/browse/CALCITE-6210, the Apache Pinot team is thinking about forbidding casting from VARCHAR to VARBINARY. I've been trying to implement that, but I'm not sure if it is possible or not. Following the Javadoc of SqlTypeCoercionRule

[question] how to do not include columns in select *

Hi there, I'm a contributor to Apache Pinot, which uses Apache Calcite under the hood. Like some other databases, Pinot defines some *private* columns that customers can use, but they are not included in select * by default. I guess this is a not so strange pattern. For example, Postgres does the