I am still not sure of what benefits we see from the new query type. As
Adrien mentioned, Lucene queries are dependent on term specific statistics.
I can imagine that this approach would save some GC cycles by reusing the
same object, but you would need to have a very large number of objects for
Hi Adrien,
Are there optimizations based on statistics that take place during the
construction process of the query?
When the query is about to be executed (passing it to the searcher) all
parameters must be bound.
So in terms of optimizations I was thinking that nothing would change.
To make su
I agree with Atri that it makes little sense to support parameterized
queries like this. Lucene not only uses field statistics but also term
statistics, so we couldn't make decisions about the right way to
execute this query before knowing what the value of `a.name` is.
Supporting something like th
Hi Atri,
Let's assume that we have the following simple SQL query over a Lucene
index holding book authors.
SELECT *
FROM authors a
WHERE a.name = ? AND a.age > 15
The where clause corresponds to a BooleanQuery combining a TermQuery and a
IntPoint query.
During the prepare phase of the SQL state
