Congratulations and welcome Julie!
On Fri, Nov 20, 2020 at 12:38 AM Mayya Sharipova
wrote:
> Congratulations and welcome Julie!!!
>
> On Thu, Nov 19, 2020 at 1:51 PM Christine Poerschke (BLOOMBERG/ LONDON) <
> cpoersc...@bloomberg.net> wrote:
>
>> Welcome Julie!
>>
>> Christine
>>
>> From:
Congratulations and welcome Julie!!!
On Thu, Nov 19, 2020 at 1:51 PM Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:
> Welcome Julie!
>
> Christine
>
> From: dev@lucene.apache.org At: 11/19/20 02:50:57
> To: dev@lucene.apache.org
> Subject: Re: Welcome Julie Tibshirani
Thanks Alan,
I've opened an issue:
https://issues.apache.org/jira/browse/LUCENE-9618
And also a PR including a unit test to demonstrate the issue:
https://github.com/apache/lucene-solr/pull/2090
Seems we're not on the exact same point, originally I'm asking about
whether nextInterval() are
Welcome Julie!
Christine
From: dev@lucene.apache.org At: 11/19/20 02:50:57To: dev@lucene.apache.org
Subject: Re: Welcome Julie Tibshirani as Lucene/Solr committer
Thank you for the warm welcome! It’s a big honor for me -- I’ve been a
Lucene fan since the start of my software career. I’m
Congratulations and welcome, Julie! :D
On Fri, Nov 20, 2020 at 2:05 AM Bruno Roustant
wrote:
> Congrats Julie!
>
> Le jeu. 19 nov. 2020 à 11:38, Alessandro Benedetti
> a écrit :
>
>> Welcome onboard Julie!
>> --
>> Alessandro Benedetti
>> Search Consultant, R Software
Congrats Julie!
Le jeu. 19 nov. 2020 à 11:38, Alessandro Benedetti a
écrit :
> Welcome onboard Julie!
> --
> Alessandro Benedetti
> Search Consultant, R Software Engineer, Director
> www.sease.io
>
>
> On Thu, 19 Nov 2020 at 03:23, Tomás Fernández Löbbe
> wrote:
>
>>
Welcome onboard Julie!
--
Alessandro Benedetti
Search Consultant, R Software Engineer, Director
www.sease.io
On Thu, 19 Nov 2020 at 03:23, Tomás Fernández Löbbe
wrote:
> Welcome Julie!
>
> On Wed, Nov 18, 2020 at 6:59 PM Ilan Ginzburg wrote:
>
>> Welcome Julie and
Some of the minimum-interval algorithms will call nextInterval() or start()
even after the interval has been exhausted, so we need to handle those
situations properly. Improved java doc would definitely be helpful though, and
maybe we should update checkIntervals() in TestIntervals to test
Hi,
I'm trying to play around with my own IntervalSource and found out that
"nextInterval" method of IntervalIterator will be called sometimes even
after "nextDoc"/"docID"/"advance" method returns NO_MORE_DOCS.
After I dug a bit more I found that FilteringIntervalIterator.reset is
calling an inner
