Hi John,
I am not sure about the way Solr implements range query.
But it looks like, that Solr is using
org.apache.lucene.search.ConstantScoreRangeQuery
which itself is using
org.apache.lucene.search.RangeFilter
So Solr do not rewrite the query to a large Boolean SHOULD, but it is
reading all t
It is a blurry line between the need to use a DBMS and lucene. For now
Lucene works fine for my search needs and I use Terracotta to persist
application state. So no need for a DBMS at all currently - although under
the hood Terracotta uses BDB JE.
Does Solr's range impementation use the large
Hi John,
about "integration other index implementation":
Sounds like you need a DBMS with some lucene features.
There was a post about using lucene in Oracle:
http://www.nabble.com/Using-lucene-as-a-database...-good-idea-or-bad-idea--to18703473.html#a18741137
and
http://www.nabble.com/Oracle-and-
27 aug 2008 kl. 11.11 skrev John Patterson:
Hi, I know that Lucene uses an inverted index which makes range
queries and
great-than/less-than type queries very slow for continuous data
types like
times, latitude, etc. Last time I looked they were converted into
huge OR
queries and so ha
