ng to keep ahead of the
requirement changes...I might actually learn this thing :).
Thanks again.
Ken
--
View this message in context:
http://lucene.472066.n3.nabble.com/Single-value-vs-multi-value-setting-in-tokenized-field-tp2268635p2294658.html
Sent from the Solr - User mailing list archive at Nabble.com.
: 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
have thought that having to support a free-form-text search, and a
> field (directed) search would be a common problem, and was just looking for
> advice.
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Single-value-vs-multi-value-setting-in-tokenized-field-tp2268635p2271543.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
d (directed) search would be a common problem, and was just looking for
advice.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Single-value-vs-multi-value-setting-in-tokenized-field-tp2268635p2271543.html
Sent from the Solr - User mailing list archive at Nabble.com.
ser@lucene.apache.org
> Sent: Sun, January 16, 2011 3:47:56 PM
> Subject: Single value vs multi value setting in tokenized field
>
>
> I have to support both general searches (free form text) and directed
> searches (field:val field2:val). To do the general search I have a fiel
y possible field in a dismax
query, I don't even know what all the fields are, new ones are added all the
time.
Has anyone got advice, suggestions on this topic (blending directed search
with general search)?
Thanks in advance,
Ken
--
View this message in context:
http://lucene.472066.n3
