I seems that you would benefit from reading at least one of the great
books on Lucene. Lucene in Action is a good place to start. Until the,
perhaps the following will be helpful
Lin Ma wrote:
- For stored field, it means its original information/structure is kept
for search results (I think for an indexed field it means means lost its
original form to indexed form), correct?
A document can have one or more fields. A field has a name and a value.
A field's value can be both stored and analyzed.
A field's value that is ONLY stored may not be used in a search query.
It may only be used as a place to hold data about the document found. A
document can have any number of stored fields.
A field's value that is ONLY analyzed can be used in a search query. It
is of no use other than for searching. A document can have nay number of
analyzed fields.
A field's value that is stored + analyzed may be used in a search query
and it's value may be retrieved from the document. A document can have
any number of stored + analyzed fields.
It must be noted that a field's value is often not useful for both
analyzing and utility after the search. In my experience the only common
reason to have a field both stored + analyzed is that during development
having the filed's value available for debugging greatly aids
discovering root problems.
- What means "phonetic fields", "phonetic serach" and "phonetic filter"?
Appreciate if you could show an example?
I don't any experience with this side Lucene. When Google fails to find
something relevant try a Delicious search. For example,
https://delicious.com/search?p=lucene%2Cphonetic
Good luck.
-- Andrew
--
Andrew Gilmartin
and...@andrewgilmartin.com
401-441-2062
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
