: I was was just a bit surprised to see that I had to go from objects to a
: string-rep.
Like i said you don't *have* do ... if you use Solr in an embeeded
context, or change your code to be a Solr plugin then you you can use
Query obecjts as is ... but when you send the data over the wire it ha
Hoss, thanks for your feedback.
I was was just a bit surprised to see that I had to go from objects to a
string-rep.
I did indeed also find out that some information was lost in that process,
for instance setMinimumNumberShouldMatch on BooleanQuery. Also,
some empty clauses (which was silently ac
: Rephrasing: I do realize that I would be able to "flatten" my Lucene
: Query-object to its String-representation and possibly use that as a query
: input to SolrQuery. But would that work for all queries ... or is the Lucene
: object-representation more expressive (i.e. richer) than the string-r
Rephrasing: I do realize that I would be able to "flatten" my Lucene
Query-object to its String-representation and possibly use that as a query
input to SolrQuery. But would that work for all queries ... or is the Lucene
object-representation more expressive (i.e. richer) than the string-rep?
Mayb
Hi,
I am process of moving from HibernateSearch (backed by Lucene) to Solr
(ditto)
in our application-
In HibernateSearch I use the Query-class provided by Lucene to build a
rather
intricate query programatically.
I would like to make my transition into Solr + Solrj as smooth as possible
and
hen
