Wait, are you saying you have fields like 2013-12-01T00:00:00Z_entryDate? So you have some wildcard definition in your schema like *_entryDate type="tdate"? If so, I think your model is just wrong and you should have some field(s) that you store dates in.
That aside, and assuming you have wildcards like I'm guessing, you could have a copyfield to like source="*_entryDate" dest="bag_of_dates" and do your ranges on "bag_of_dates". Which would be the same as putting your dates in a single field with a fixed name in the first place. Best, Erick On Sun, Oct 6, 2013 at 4:34 PM, Darniz <rnizamud...@edmunds.com> wrote: > Thanks Eric. > > i hope i understood correctly, but my main concern is i have to tie specific > content indexed to a specific time range. and make that document come up in > search results only for that time. As i have mentioned in my previous > example we have multiple data-string structures which makes a bit more > complicated, on top of that i don't know what will be the exact date. Hence > if someone searches for toyota and if today is 6-OCT-2013 this doc should > not come in search results since the keyword toyota should be searched only > after 1-DEC-2013. > > <date name="2013-09-01T00:00:00Z_entryDate">2013-09-01T00:00:00Z</date> > <str name="2013-09-01T0:00:00Z_entryText">Sept content : Honda is releasing > the car this month </str> > > <date name="2013-12-01T00:00:00Z_entryDate">2013-12-01T00:00:00Z</date> > <str name="2013-12-01T00:00:00Z_entryText">Dec content : Toyota is releasing > the car this month </str> > > i dont know using a copy field might solve this or correct me if i am wrong. > > may be we are pursuing something which is not meant for Solr. > > Thanks > Rashid > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Doing-time-sensitive-search-in-solr-tp4092273p4093790.html > Sent from the Solr - User mailing list archive at Nabble.com.
