On Fri, Jan 1, 2010 at 9:47 PM, JaredM <emru...@gmail.com> wrote: > > Thanks Ahmet and Israel. I prefer Israel's approach since the amount of > metadata for the user is quite high but I'm not clear how to get around one > problem: > > If I had 2 availabilities (I've left it in human-readable form instead of > as > a UNIX timestamp only for ease of understanding): > > <field name="start_date">10-Jan-2010</field> > <field name="start_date">20-Jan-2010</field> > <field name="end_date">25-Jan-2010</field> > <field name="end_date">28-Jan-2010</field> > > and I wanted to query for availability between 12-Jan-2010 to 26-Jan-2010 > then then wouldn't the above document be returned (even though the use > would > not be available 20-25 Jan? > -- > View this message in context: > http://old.nabble.com/Help-with-creating-a-solr-schema-tp26979319p26990178.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
Unfortunately, For this particular use case, if you are using the out-of-the-box features available in Solr 1.4, without a custom Solr plugin using a custom Lucene filter and some special value storage arrangement for the fields, you will have to store each start and end date as a separate document. So, there will be N separate documents for each username if that user has N distinct periods of availabilty. The start date and end date fields would also have to be single valued instead of multi-valued as I specified in the earlier post. Sorry. -- "Good Enough" is not good enough. To give anything less than your best is to sacrifice the gift. Quality First. Measure Twice. Cut Once. http://www.israelekpo.com/
