lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kenf_nc <ken.fos...@realestate.com>
Subject Re: Single value vs multi value setting in tokenized field
Date Mon, 17 Jan 2011 10:50:42 GMT

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
'content' field hold data like:
   some description maybe a paragraph or two
   a product or service title
   tag1
   tag2
   feature1
   feature2
or would it be better to make it a concatenated, single value field like:
     some description maybe a paragraph or two a product or service title
tag1 tag2 feature1 feature2

my indexing seems to take longer than most, it takes about 2 1/2 hours to
index 3.5 million records. I have a colleague that, in a separate project,
is indexing 70 million records in about 4 hours, albeit in a much simpler
schema. So I'm trying to see if this could be a factor in my indexing
performance. I also wanted to know what impact, in general, not just in this
situation, using a MultiValued field versus a Single Valued field has in
search results.

I would 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.

Mime
View raw message