Gora, currently our core does use mult-valued fields. however the exsiting multi-valued fields in the schema are will only result in 3 - 10 values.
we are thinking of using the text blob approach primarily because of the large number of possible values in this field. if we were to use a multi-valued field, it is likely that the MV field would have 200+ values and in some edge cases 400+ values. are you saying that the MV field approach to represent the data (given the scale previously indicated) is the best design solution? -- View this message in context: http://lucene.472066.n3.nabble.com/large-text-blobs-in-string-field-tp4017882p4018315.html Sent from the Solr - User mailing list archive at Nabble.com.
