lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Lea <ian....@gmail.com>
Subject Re: Can I still use SearcherManager in this situation?
Date Wed, 07 Nov 2012 12:10:15 GMT
Sorry, didn't notice that refreshIfNeeded is protected.  You could run
IndexUpgrader on your old indexes to bring them up to date, in stages
from v2 to v3 then v4, then upgrade.


--
Ian.


On Wed, Nov 7, 2012 at 12:04 PM, Trejkaz <trejkaz@trypticon.org> wrote:
> On Wed, Nov 7, 2012 at 10:11 PM, Ian Lea <ian.lea@gmail.com> wrote:
>> 4.0 has maybeRefreshBlocking which "is useful if you want to guarantee
>> that the next call to acquire() will return a refreshed instance".
>> You don't say what version you're using.
>>
>> If you're stuck on 3.6.1 can you do something with refreshIfNeeded()
>> or isSearcherCurrent()?
>
> Ah, yes. I'm stuck on 3.6 at the moment (for backwards compatibility
> with v2 indexes.) refreshIfNeeded() might work, but it's protected so
> I will have to subclass to make it public (and hope that nothing bad
> happens by accessing it directly.)
>
> TX
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message