Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-16 Thread Erick Erickson
jmlucjav > Sent: Saturday, December 15, 2012 6:04 AM > > To: solr-user@lucene.apache.org > Subject: Re: optimun precisionStep for DAY granularity in a TrieDateField > > without going through such rigorous testing, maybe for my case (interested > only in DAY), I could jus

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-15 Thread Jack Krupansky
er 15, 2012 6:04 AM To: solr-user@lucene.apache.org Subject: Re: optimun precisionStep for DAY granularity in a TrieDateField without going through such rigorous testing, maybe for my case (interested only in DAY), I could just index the trielong values such as 20121010, 20110101 etc... This would

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-15 Thread jmlucjav
without going through such rigorous testing, maybe for my case (interested only in DAY), I could just index the trielong values such as 20121010, 20110101 etc... This would take less space than trieDate (I guess), and I still have a date looking number (for easier handling). I could even base the

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-14 Thread Shawn Heisey
On 12/14/2012 4:15 PM, Jack Krupansky wrote: And the "official" answer when I posed the question on the Lucene User list is that the time of day bits would still be stored in the index in spite of the precisionStep. So, it doesn't really matter very much at all what precisionStep you use for tr

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-14 Thread Jack Krupansky
Jack Krupansky -Original Message- From: Jack Krupansky Sent: Friday, December 14, 2012 5:48 PM To: solr-user@lucene.apache.org Subject: Re: optimun precisionStep for DAY granularity in a TrieDateField I've tried to figure this out and haven't fully resolved it. I mean, sure, you can se

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-14 Thread Jack Krupansky
I've tried to figure this out and haven't fully resolved it. I mean, sure, you can set the precisionStep to 26, which may ignore the milliseconds per day, but supposedly it makes it much slower to lookup and may not actually throw away those 26 bits. -- Jack Krupansky -Original Message---

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-14 Thread jmlucjav
thanks Lance. I new about rounding in the request params, but I want to know if there is something to tweak at indexing time (by changing precisionSteop in schema.xml) in order to store only needed information. At query time yes, I would round to /DAY -- View this message in context: http://l

Re: optimun precisionStep for DAY granularity in a TrieDateField

2012-12-14 Thread Lance Norskog
Do you use rounding in your dates? You can index a date rounded to the nearest minute, N minutes, hour or day. This way a range query has to look at such a small number of terms that you may not need to tune the precision step. Hunt for NOW/DAY or 5DAYS in the queries. http://wiki.apache.org/s