Re: Ignite for Parquet files

2023-06-30 Thread Arunima Barik
Are there any provisions wherein I can discuss about my project implementation with someone from the Ignite team to clarify some doubts? Preferably through a small online meet? Regards Arunima On Sat, 1 Jul, 2023, 12:03 am Jeremy McMillan, wrote: > Python doesn't at this time go anywhere near

Re: Ignite for Parquet files

2023-06-30 Thread Jeremy McMillan
Python doesn't at this time go anywhere near Ignite CacheStore. You would need to implement the CacheStore in Java or some other language which compiles to JVM runtime/jar. There's a talk from the most recent summit on using Groovy, if you want a higher level language than Java, but theoretically y

Re: Ignite for Parquet files

2023-06-30 Thread Arunima Barik
Which do you think would be a better option? Federated queries or CacheStore And is CacheStore supported in Python? On Fri, 30 Jun, 2023, 1:50 pm Stephen Darlington, < stephen.darling...@gridgain.com> wrote: > You’d need to implement your own Cache Store. > https://ignite.apache.org/docs/latest

Re: SetLoacl is not work for Calcite

2023-06-30 Thread Stephen Darlington
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

Re: Re: SetLoacl is not work for Calcite

2023-06-30 Thread Alex Plehanov
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

Re: Re: SetLoacl is not work for Calcite

2023-06-30 Thread Hitesh Nandwana
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

Re: Re: SetLoacl is not work for Calcite

2023-06-30 Thread Alex Plehanov
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

Re:Re: SetLoacl is not work for Calcite

2023-06-30 Thread y
Thanks for your suggestion. We are considering the feasibility of your proposed solution. For complex business production environments, it is difficult to distinguish whether the query requires setLocal or not. Anyway, thank you for your help. At 2023-06-30 15:18:07, "Stephen Darli

Re: Ignite for Parquet files

2023-06-30 Thread Stephen Darlington
You’d need to implement your own Cache Store. https://ignite.apache.org/docs/latest/persistence/custom-cache-store > On 30 Jun 2023, at 06:46, Arunima Barik wrote: > > > -- Forwarded message - > From: Arunima Barik > > Date: Fri, 30 Jun, 2023,

Re: SetLoacl is not work for Calcite

2023-06-30 Thread Stephen Darlington
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