On 5/16/07, Jack L <[EMAIL PROTECTED]> wrote:
The doc describes the purpose of copyField as:
"This is provided as a convenient way to ensure that data is
put into several fields, without needing to include the data in
the update command multiple times."
It sounds like many to many copying. What is the intended use case
for this?
The example schema.xml is better at pointing out that there are two use cases:
<!-- copyField commands copy one field to another at the time a document
is added to the index. It's used either to index the same
field differently,
or to add multiple fields to the same field for easier/faster searching.
-->
<copyField source="id" dest="sku"/>
<copyField source="cat" dest="text"/>
<copyField source="name" dest="text"/>
<copyField source="name" dest="nameSort"/>
<copyField source="name" dest="alphaNameSort"/>
<copyField source="manu" dest="text"/>
<copyField source="features" dest="text"/>
<copyField source="includes" dest="text"/>
<copyField source="manu" dest="manu_exact"/>
This seems to be able to resolve both of my problems (multiple
default search fields and field boost.) If my understanding is
correct, it should be a more useful RequestHandler for probably
most solr uses.
It is not the default though.
It came later... "standard" was the first request handler.
dismax is the recommended starting point for anyone dealing with user
entered queries:
http://wiki.apache.org/solr/SolrRelevancyFAQ
The documentation is slowly improving :-)
-Yonik
