ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Mashenkov <andrey.mashen...@gmail.com>
Subject Re: IGNITE-5468 ticket description looks confusing.
Date Wed, 05 Jul 2017 09:16:57 GMT
Yes, Yakov. I mean query with join of 2 caches can be run on either of it.

Second parameter is merge prefetch size. You can see they going together in

5 июля 2017 г. 11:48 пользователь "Yakov Zhdanov" <yzhdanov@apache.org>

> Same query against different caches? This sounds like same query against
> different tables. :) Andrey can you please provide real-world example?
> What 2 params do you mean? Which one is the second?
> My points are:
> - provide ability to set limits without restarting the cluster.
> - provide ability to set limits per query as different queries may require
> different resources and having one hard limit for all the queries seems to
> be very inconvenient.
> Ideally, I would get rid of this IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> and use just memory limits - if query runs out of memory then it is
> cancelled with proper error message, but I doubt if this can be done
> quickly.
> --
> Yakov Zhdanov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message