> What does a lot mean? How high is the sky? If I have 3 milion docs I would end up with 3 milion * days avaliable
> This can be done. And given that you want long stretches of availability, > but what happens when a reservation is canceled? You have to coalesce > intervals. That isn't impossible, but it is a pain. > > Would this count as premature optimization? I always build the index from scratch indexing from an external datasource, getting the avaliability from there (and all the other data from a document) > If you want to drive down to a resolution of seconds, the document time > slot > model doesn't work. But for days, it probably does. yes, the avaliability is defined per days, not per seconds. I'm trying to find the way to make this perform as better as possible. I've found this and it's interesting too: https://issues.apache.org/jira/browse/SOLR-1913 But the only way I see to use it is generate dinamic fields per month and filter using them. The problem here is that for each month I want to filter a search request, I would have to load a FieldCache.getInts and will quickly run OOM. -- View this message in context: http://lucene.472066.n3.nabble.com/Search-calendar-avaliability-tp3457203p3457899.html Sent from the Solr - User mailing list archive at Nabble.com.
