Why do you care about redundancy? That's the search engine's architectural tradeoff (as far as I understand). And, the tokens are all normalized under the covers, so it does not take as much space as you expect.
Specifically regarding your issue, maybe you should store 'occupancy' as the record. That's similar to what they do at Gilt: http://www.slideshare.net/trenaman/personalized-search-on-the-largest-flash-sale-site-in-america(slide 36+) The other option is to use location as spans with some clever queries: http://wiki.apache.org/solr/SpatialForTimeDurations (follow the links). Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Thu, Jul 18, 2013 at 5:58 PM, SolrLover <bbar...@gmail.com> wrote: > > I am trying to implement Historical search using SOLR. > > Ex: > > If I search on address 800 5th Ave and provide a time range, it should list > the name of the person who was living at the address during the time > period. > I am trying to figure out a way to store the data without redundancy. > > I can do a join in the database to return all the names who were living in > a > particular address during a particular time but I know it's difficult to do > that in SOLR and SOLR is not a database (it works best when the data is > denormalized).,.. > > Is there any other way / idea by which I can reduce the redundancy of > creating multiple records for a particular person again and again? > > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Need-ideas-to-perform-historical-search-tp4078980.html > Sent from the Solr - User mailing list archive at Nabble.com. >
