Another option is to model this problem in Solr with an even more
denormalized schema: you have one document per person per day. So,
instead of:
id=0 user=Alice start_date:1-Jan-2010 end_date:5-Jan-2010
you have:
id=0 user=Alice date:1-Jan-2010
id=1 user=Alice date:2-Jan-2010
id=2 user=Alice date:
On Fri, Jan 1, 2010 at 9:47 PM, JaredM 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
>
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):
10-Jan-2010
On Thu, Dec 31, 2009 at 10:26 AM, JaredM wrote:
>
> Hi,
>
> I'm new to Solr but so far I think its great. I've spent 2 weeks reading
> through the wiki and mailing list info.
>
> I have a use case and I'm not sure what the best way is to implement it. I
> am keeping track of peoples calendar sc
> Hi,
>
> I'm new to Solr but so far I think its great. I've
> spent 2 weeks reading
> through the wiki and mailing list info.
>
> I have a use case and I'm not sure what the best way is to
> implement it. I
> am keeping track of peoples calendar schedules in a really
> simple way: each
> user
