the system if a new user is to be given access to an already indexed
document(and I figure that this will happen frequently in the system). Is
there a better approach that I can take?
Thanks,
Murali
Thanks for your reply. But your suggestion is not applicable to my situation
because 'users' of our system dont correspond to unix users, and different
users are not related in any way, so there is no logical way to split them
into groups.
Murali
On 12/21/05, Mordo, Aviran (EXP
s to the system will be added continually.
Thanks,
Murali
On 12/27/05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> There is no officially released 1.9 version yet. Many people are
> using the current 1.9 branch for production, however, and it is stable
> (moreso than 1.4.3 IMO).
Why hasn't there been a release since 1.4.3(11/29/04)? Is there a date set
Hi,
I would like to know if there is any automatic eviction policy for the
field cache entries. I understand that it gets invalidated when a new
searcher opens. But, my question is in case if gc runs or if there is any
other scenario which could evict the unused entries from fieldcache.
Please he
; for legacy indexes where the schema was not updated to use DocValues. In
> an "ideally configured Solr server", the Admin UI shows no entries below
> Core's FieldCache stats. If you see entries there go and replace those
> field's config by adding docvalues=true.
>
h the whole cache has to be
> rebuilt. This is also one reason why DocValues are preferred for sorting.
>
>
https://2012.berlinbuzzwords.de/sessions/your-index-reader-really-atomic-or-maybe-slow.html
>
> https://www.youtube.com/watch?v=iZZ1AbJ6dik
>
> Uwe
>
> Am 08.06.2022 u
