Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+eZwrHxeheyc1M-K7TXfz58vy0hNWGs95jhppS_SdG5WM2MMA@mail.gmail.com>
References: 
 <CAGt6o8m2W6=QZ203Y4ZwhQxMEHLpZ8eXq_EXHkEW9RHfenqvuA@mail.gmail.com>
 <531879978.833701.1444919200482.JavaMail.yahoo@mail.yahoo.com>
 <CA+eZwrHxeheyc1M-K7TXfz58vy0hNWGs95jhppS_SdG5WM2MMA@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Thu, 15 Oct 2015 08:41:15 -0700
Message-ID: 
 <CA+0=VoVM8AGX2pfodH1ZKRSF_R+S2gf96cbv=utBHGfAnmRW6A@mail.gmail.com>
Subject: Re: Do we need "IgniteCache.randomEntry()" method?
To: dev@ignite.apache.org
Cc: Roman <rshtykh@yahoo.com>
Content-Type: multipart/alternative; boundary=001a113d841abf1f2c0522268425

--001a113d841abf1f2c0522268425
Content-Type: text/plain; charset=UTF-8

I agree that method randomEntry() can be deprecated. However, in that case
we should also deprecate RandomEvictionPolicy, which probably is used in
some tests.

Does anyone see any potential issues here?

D.

On Thu, Oct 15, 2015 at 7:37 AM, Sergi Vladykin <sergi.vladykin@gmail.com>
wrote:

> Agree, it is doubtfully useful.
>
> Sergi
>
> 2015-10-15 17:26 GMT+03:00 Roman <rshtykh@yahoo.com.invalid>:
>
> > And another ticket for randomEntry()
> > https://issues.apache.org/jira/browse/IGNITE-1180
> >
> >
> >      On Thursday, October 15, 2015 9:47 PM, Vladimir Ozerov <
> > vozerov@gridgain.com> wrote:
> >
> >
> >  Igniters,
> >
> > We have the ticket about broken randomEntry() method:
> > https://issues.apache.org/jira/browse/IGNITE-512
> >
> > This method can return null even if cache is not empty. And it is even
> > impossible to return an entry in constant time provided that concurrent
> > deletes and expirations could occur.
> >
> > Do we really need this method? As for me it is better to deprecate it and
> > do not spend any efforts trying to make it work.
> >
> > Thoughts?
> >
> >
> >
> >
>

--001a113d841abf1f2c0522268425--