I’m curious: why did you switch to Calcite if your deployment is in production?
I would generally be cautious about putting beta software into production. Was
there some critical feature that you needed?
> On 30 Jun 2023, at 09:34, y wrote:
>
> Thanks for your suggestion. We are considering t
Hitesh,
To unsubscribe, send a message to user-unsubscr...@ignite.apache.org
(not to user@ignite.apache.org).
пт, 30 июн. 2023 г. в 13:50, Hitesh Nandwana :
>
> Why It is not subscribing?
>
> On Fri, 30 Jun, 2023, 14:17 Alex Plehanov, wrote:
>>
>> Hello,
>>
>> Patch to support setLocal flag for
Why It is not subscribing?
On Fri, 30 Jun, 2023, 14:17 Alex Plehanov, wrote:
> Hello,
>
> Patch to support setLocal flag for the calcite engine will be merged
> soon (see ticket [1]).
>
> [1] https://issues.apache.org/jira/browse/IGNITE-19725
>
> пт, 30 июн. 2023 г. в 13:35, y :
> >
> > Thanks f
Hello,
Patch to support setLocal flag for the calcite engine will be merged
soon (see ticket [1]).
[1] https://issues.apache.org/jira/browse/IGNITE-19725
пт, 30 июн. 2023 г. в 13:35, y :
>
> Thanks for your suggestion. We are considering the feasibility of your
> proposed solution. For complex
If this is an important feature for you, the obvious solution would be to use
the H2 SQL engine (which is still the default, since the Calcite engine is
still considered beta).
As noted in the documentation, you can even keep Calcite as the default engine
in your cluster and only route these qu
Hello,
The Calcite-based SQL engine currently doesn't analyze any properties
of SqlFieldsQuery except "Sql", "Schema", "Args" and
"QueryInitiatorId". Some of the rest properties are useless for the
Calcite-based engine at all (for example, "DistributedJoins", since
all joins in the Calcite-based e
