Sorry, I intended to design my post so that one wouldn't have to read the thread for context but it seems I failed to do that. Don't bother reading the thread. The use-case I'm pondering modifying Lucene/Solr to solve is the one-to-many problem. Imagine a document that contains multiple addresses where each field of an address (like street, state, zipcode) go in different multi-valued fields. The main difficulty is considering how Lucene might be modified to have query results across different fields be intersected by a matching term position offset (which is designed in these fields to refer to a known value offset).
Following the link you gave is interesting though the general case I'm talking about doesn't have a hierarchy. And I find the use of a single multi-valued field unpalatable for a variety of reasons. ~ David Smiley ----- Author: https://www.packtpub.com/solr-1-4-enterprise-search-server/book -- View this message in context: http://n3.nabble.com/One-item-multiple-fields-and-range-queries-tp475030p683361.html Sent from the Solr - User mailing list archive at Nabble.com.
