ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Entry filter in IgniteCache#loadCache
Date Mon, 20 Feb 2017 12:15:35 GMT
+1

On Sat, Feb 18, 2017 at 11:51 PM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:

> Igniters,
>
> Currently IgniteCache.loadCache has optional entry filter that can be
> passed as an argument. It seems to be redundant because:
>
>    - Filtering that is done by this filter can be as well implemented
>    within CacheStore itself. Moreover, if the filtering can be done on DB
>    level, it's better from performance standpoint.
>    - In case filtering has to be dynamic (i.e. use does wants to provide a
>    predicate as an argument), generic arguments can be used.
>
> Having said that, this predicate doesn't add any value and therefore
> creates confusion. And frankly, I've never seen anyone using it. I suggest
> to remove it completely in 2.0.
>
> Thoughts?
>
> -Val
>

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