On September 2 Courtney will tell more about Hypi use case, join us at
Virtual Meetup:
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/280030600/
Below I quote Courtney's email to the user list:
The talk will look at the general architecture, playing nice with other
> technologies and
Hi Courtney,
Statistics for query planning is a rather complex subject.
Unfortunately I am now aware of technical details how is it expected
to be implemented in Ignite 3.
Folks driving SQL please step in.
2021-07-31 20:18 GMT+03:00, Courtney Robinson :
> Hi Ivan,
> Atri's description of the que
Hi Ivan,
Atri's description of the query plan being cached is what I was thinking of
with my description.
I lack the knowledge on how the statistics are maintained to really comment
constructively Atri but my first question about the problem you raise with
statistics would be:
How/where are the s
Query caching works on three levels - caching results, caching blocks and
caching query plans.
Prepared queries work by caching a plan for a query and reusing that plan
by changing the parameters for the incoming query. So the query remains the
same, but input values keep changing.
The problem wi
Hi Courtney,
Please clarify what do you mean by prepared queries and query caching?
Do you mean caching query results? If so, in my mind material views
are the best approach here (Ignite 2 does not support them). Do you
have other good approaches in your mind? E.g. implemented in other
databases.
Hi Courtney,
Generally speaking, query caching certainly makes sense. As far as I know,
Ignite 2.x actually does that, but most likely there might be room for
improvement as well. We will look into this.
As for the SQL API - the answer is yes. The requirement for a dummy cache
is an artifact of t
Something else came to mind, are there plans to support prepared queries?
I recall someone saying before that Ignite does internally cache queries
but it's not at all clear if or how it does do that. I assume a simple hash
of the query isn't enough.
We generate SQL queries based on user runtime s
Andrey,
Thanks for the response - see my comments inline.
> I've gone through the questions and have no the whole picture of your use
> case.
Would you please clarify how you exactly use the Ignite? what are the
> integration points?
>
I'll try to clarify - we have a low/no code platform. A use
Courtney,
I have a short update.
> 3. The Lucene API enabled more flexibility and removed a network
> round trip from our queries.
> 4. Given Calcite's ability to support custom SQL functions, I'd love
> to have the ability to define custom functions that Lucene was
answering
As w
Hi Courtney,
Thanks for your feedback.
I've gone through the questions and have no the whole picture of your use
case.
Would you please clarify how you exactly use the Ignite? what are the
integration points?
and maybe share some experience with using Ignite SPIs?
We'll keep the information in m
Hey everyone,
I attended the Alpha 2 update yesterday and was quite pleased to see the
progress on things so far. So first, congratulations to everyone on the
work being put in and thank you to Val and Kseniya for running yesterday's
event.
I asked a few questions after the webinar which Val had s
11 matches
Mail list logo
