multiValued fields retain their order, for the record.
Erik
On Sep 4, 2007, at 12:37 AM, Jed Reynolds wrote:
One of the difficulties that you're going to find with multi-valued
fields is that they are an unordered collection without relation.
If you have a document with a list of
approach to the problem?
Thanks
Bharani
--
View this message in context:
http://www.nabble.com/Multiple-Values--Structured--tf4370282.html#a12456399
Sent from the Solr - User mailing list archive at Nabble.com.
://www.nabble.com/Multiple-Values--Structured--tf4370282.html#a12456399
Sent from the Solr - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/Multiple-Values--Structured--tf4370282.html#a12479706
Sent from the Solr - User mailing list archive at Nabble.com.
are out of
order, that might make a significant different.
I would create a document per revision and take advantage of range
queries and sorting available at the query level.
Jed
--
View this message in context:
http://www.nabble.com/Multiple-Values--Structured--tf4370282.html
Bharani wrote:
Hi,
I have got two sets of document
1) Primary Document
2) Occurrences of primary document
Since there is no such thing as join i can either
a) Post the primary document with occurrences as multi valued field
or
b) Post the primary document for every occurrences i.e.
number of documents and even if i try
with index only and not store i am still have to deal with duplicate hit -
becuase all i want is the primary document
Is there a better approach to the problem?
Thanks
Bharani
--
View this message in context:
http://www.nabble.com/Multiple-Values--Structured
