In my case, for any non-trivial search, I always build a boolean query
with relevant parsing for each field, where applicable using something
like oal.queryparser.classic.QueryParser.
So if I had some free text docs with a date field, the latter stored
as you suggest, and a query along the lines o
Ok... so how does anyone ever use date-time queries in lucene with the
new recommended way of using longs?
Jon
On Wed, Feb 11, 2015 at 9:26 AM, Ian Lea wrote:
> Ah well, you've got me there. I'm not a lucene developer and rather
> thought that I'd leave the implementation as an exercise for t
Ah well, you've got me there. I'm not a lucene developer and rather
thought that I'd leave the implementation as an exercise for the
reader. Good luck!
--
Ian.
On Wed, Feb 11, 2015 at 2:20 PM, Jon Stewart
wrote:
> Eek. So is there a parsing component somewhere that gets handed a
> field name
Eek. So is there a parsing component somewhere that gets handed a
field name and query components (e.g., "created", "2010-01-01",
"2014-12-31"), which I can derive from, parse the timestamp strings,
and then turn the whole thing into a numeric range query component?
Jon
On Wed, Feb 11, 2015 at
To the best of my knowledge you are spot on with everything you say,
except that the component to parse the strings doesn't exist. I
suspect that a contribution to add that to StandardQueryParser might
well be accepted.
--
Ian.
On Wed, Feb 11, 2015 at 4:21 AM, Jon Stewart
wrote:
> Hello,
>
>
Hello,
I've done a lot of googling, but haven't stumbled upon the magic
answer: how does one use StandardQueryParser with numeric fields
representing timestamps, to allow for range queries?
When indexing, my timestamp fields are ISO 8601 strings. I'm parsing
them and then storing the milliseconds
