Re: multiple dateranges/timeslots per doc: modeling openinghours.

: This would need 2*3*100 = 600 dynamicfields to cover the openinghours. You : mention this is peanuts for constructing a booleanquery, but how about : memory consumption? : I'm particularly concerned about the Lucene FieldCache getting populated for : each of the 600 fields. (Since I had some nas

Re: multiple dateranges/timeslots per doc: modeling openinghours.

Op 11 oktober 2011 03:21 schreef Chris Hostetter het volgende: > > : Conceptually > : the Join-approach looks like it would work from paper, although I'm not a > : big fan of introducing a lot of complexity to the frontend / querying > part > : of the solution. > > you lost me there -- i don't see

Re: multiple dateranges/timeslots per doc: modeling openinghours.

: Conceptually : the Join-approach looks like it would work from paper, although I'm not a : big fan of introducing a lot of complexity to the frontend / querying part : of the solution. you lost me there -- i don't see how using join would impact the front end / query side at all. your query c

Re: multiple dateranges/timeslots per doc: modeling openinghours.

On Mon, Oct 3, 2011 at 3:09 PM, Geert-Jan Brits wrote: > Interesting! Reading your previous blogposts, I gather that the to be > posted > 'implementation approaches' includes a way of making the SpanQueries > available within SOLR? > It's going to be posted in two days. But please don't expect m

Re: multiple dateranges/timeslots per doc: modeling openinghours.

Thanks Hoss for that in-depth walkthrough. I like your solution of using (something akin to) FieldMaskingSpanQuery. Conceptually the Join-approach looks like it would work from paper, although

Re: multiple dateranges/timeslots per doc: modeling openinghours.

Interesting! Reading your previous blogposts, I gather that the to be posted 'implementation approaches' includes a way of making the SpanQueries available within SOLR? Also, would with your approach would (numeric) RangeQueries be possible as Hoss suggests? Looking forward to that 'implementation

Re: multiple dateranges/timeslots per doc: modeling openinghours.

I agree about SpanQueries. It's a viable measure against "false-positive matches on multivalue fields". we've implemented this approach some time ago. Pls find details at http://blog.griddynamics.com/2011/06/solr-experience-search-parent-child.html and http://blog.griddynamics.com/2011/07/solr-ex

Re: multiple dateranges/timeslots per doc: modeling openinghours.

: Another, faulty, option would be to model opening/closing hours in 2 : multivalued date-fields, i.e: open, close. and insert open/close for each : day, e.g: : : open: 2011-11-08:1800 - close: 2011-11-09:0300 : open: 2011-11-09:1700 - close: 2011-11-10:0500 : open: 2011-11-10:1700 - close: 2011

Re: multiple dateranges/timeslots per doc: modeling openinghours.

-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/multiple-dateranges-timeslots-per-doc-modeling-openinghours-tp3368790p3371747.html Sent from the Solr - User mailing list archive at Nabble.com.

multiple dateranges/timeslots per doc: modeling openinghours.

roach is at all feasible. - if option C. would suffice. (excluding REQ 3. ), and if I'm likely to run into performance / memory troubles. - any other possible solutions I haven' thought of to tackle this. Thanks a lot. Cheers, Geert-Jan -- View this message in context: http://lucene.472066.n3.nabble.com/multiple-dateranges-timeslots-per-doc-modeling-openinghours-tp3368790p3368790.html Sent from the Solr - User mailing list archive at Nabble.com.