Thanks guys. I read (and actually digested this time) how multivalued fields
work and now realize my question came from a 'structured language/dbms'
background. The multivalued field is stored basically as a single value with
extra spacing between terms (the positionIncrementGap previously mention
: problem, disk space is cheap. What I wanted to know was whether it is best
: to make the single field multiValued="true" or not. That is, should my
: 'content' field hold data like:
...
: or would it be better to make it a concatenated, single value field like:
functionally, the only di
Functionally, the two options are equivalent, and I've never really
heard of any speed difference. Assuming it's not that big a programming
change, though, you probably want to just test...
Do be aware of one subtle difference in the approaches, though. If the
increment gap is != 1 then multiValue
No, I have both, a single field (for free form text search), and individual
fields (for directed search). I already duplicate the data and that's not a
problem, disk space is cheap. What I wanted to know was whether it is best
to make the single field multiValued="true" or not. That is, should my
Hi,
I'm not a big fan of putting all fields in a single field (bye bye dismax, as
you say), but if you are asking whether doing it via copyField or "directly" is
will make a difference - not really.
If you do it with copyField, you still get to keep your individual fields,
which
could serve yo
