Erick Erickson wrote:
As Miles said, use the DateTools (lucene) class with a DAY resolution.
That'll give you a MMDD format, which won't blow your query with a
"TooManyClauses" exception...
Remember that Lucene deals with strings, so you want to store things in
easily-manipulated string
As Miles said, use the DateTools (lucene) class with a DAY resolution.
That'll give you a MMDD format, which won't blow your query with a
"TooManyClauses" exception...
Remember that Lucene deals with strings, so you want to store things in
easily-manipulated string format, often one that'
Michael J. Prichard wrote:
Miles Barr wrote:
Michael J. Prichard wrote:
I am working on indexing emails and have stored the data as
milliseconds. I was thinking of using a filter w/ my search that
would only return the email in that data range. I am currently
indexing as follows:
doc.a
two ideas:
1> store a second field that contains the time resolution you need, and sort
by that. You can still search (quickly) by the day-resolution field.
2> If you KNOW that you are indexing the e-mails in time-order, then sorting
by doc_id will preserve the time ordering.
Erick
Michael J. Prichard wrote:
I guess the more I think about it I don't really care about the
minutes in the initial. All that matters is the date (i.e.
2006-07-25). The only thing I would need the time for would be for
sorting so I need to have that too. Ideas?
Store as much detail as you
Miles Barr wrote:
Michael J. Prichard wrote:
I am working on indexing emails and have stored the data as
milliseconds. I was thinking of using a filter w/ my search that
would only return the email in that data range. I am currently
indexing as follows:
doc.add(new Field("date", (String)
Michael J. Prichard wrote:
I am working on indexing emails and have stored the data as
milliseconds. I was thinking of using a filter w/ my search that
would only return the email in that data range. I am currently
indexing as follows:
doc.add(new Field("date", (String) itemContent.get("da
