Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of bernd.fehling@uni-bielefeld.de
 designates 129.70.204.73 as permitted sender)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=ISO-8859-15; format=flowed
Date: Tue, 21 Jun 2011 11:32:27 +0200
From: Bernd Fehling <bernd.fehling@uni-bielefeld.de>
Subject: questions about fieldCache
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
Message-id: 
 <780_1308648748_ZZh0u11fzJ~dL.00_4E00652B.6010903@uni-bielefeld.de>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.17) Gecko/20110414
 SUSE/3.1.10 Thunderbird/3.1.10

I'm trying to understand the logic of/behind fieldCache.

Who has written this peace of code or has good knowledge about it?

Why is it under the hood of jetty?

I see FieldCache$StringIndex with
- f_dccollection
- f_dcyear
- f_dctype
but also
- dctitle --> f_dctitle --> f_dccreator
- title --> f_dcyear

There are some entries without further reference like the first examples
and some that have references to further HashMaps like a chain.
Why is it this way, what is the purpose?

What is fieldCache doing if a server is replicated, will all old content
be cleaned up because of a new index with new content?

Regards
Bernd


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