Any Copy Field Caveats?

[Will Milspec <wi...@gmail.com>]

Hi all,

we're moving from an old lucene version to solr  and plan to use the "Copy
Field" functionality. Previously we had "rolled our own" implementation,
sticking title, description, etc. in a field called 'content'.

We lose some flexibility (i.e. java layer can no longer control what gets in
the new copied field), at the expense of simplicity. A fair tradeoff IMO.

My question: has anyone found any subtle issues or "gotchas" with copy
fields?

(from the subject line "caveat"--pronounced 'kah-VEY-AT'  is Latin as in
"Caveat Emptor"..."let the buyer beware").

thanks,

will

will

Re: Any Copy Field Caveats?

[Erick Erickson <er...@gmail.com>]

It's pretty straight-forward, just make sure your dest field has
multivalued="true"....

Do note that the *raw* data is copied, not the analyzed. Conceptually
the copy is done before analysis of the source field (which you probably
already know, but the question has come up on the list from time to time).

Best
Erick


On Fri, Nov 5, 2010 at 11:02 AM, Will Milspec <wi...@gmail.com>wrote:

> Hi all,
>
> we're moving from an old lucene version to solr  and plan to use the "Copy
> Field" functionality. Previously we had "rolled our own" implementation,
> sticking title, description, etc. in a field called 'content'.
>
> We lose some flexibility (i.e. java layer can no longer control what gets
> in
> the new copied field), at the expense of simplicity. A fair tradeoff IMO.
>
> My question: has anyone found any subtle issues or "gotchas" with copy
> fields?
>
> (from the subject line "caveat"--pronounced 'kah-VEY-AT'  is Latin as in
> "Caveat Emptor"..."let the buyer beware").
>
> thanks,
>
> will
>
> will
>

Re: Any Copy Field Caveats?

[Tod <li...@gmail.com>]

I've noticed that using camelCase in field names causes problems.


On 11/5/2010 11:02 AM, Will Milspec wrote:
> Hi all,
>
> we're moving from an old lucene version to solr  and plan to use the "Copy
> Field" functionality. Previously we had "rolled our own" implementation,
> sticking title, description, etc. in a field called 'content'.
>
> We lose some flexibility (i.e. java layer can no longer control what gets in
> the new copied field), at the expense of simplicity. A fair tradeoff IMO.
>
> My question: has anyone found any subtle issues or "gotchas" with copy
> fields?
>
> (from the subject line "caveat"--pronounced 'kah-VEY-AT'  is Latin as in
> "Caveat Emptor"..."let the buyer beware").
>
> thanks,
>
> will
>
> will
>