On Fri, Mar 13, 2009 at 9:56 PM, Jon Baer jonb...@gmail.com wrote:
Bare in mind (and correct me if Im wrong) but a full-import is still a
full-import no matter what entity you tack onto the param.
Thus I think clean=false should be appended (a friend starting off in Solr
was really confused
On Fri, Mar 13, 2009 at 12:03 AM, Narayanan, Karthikeyan
karthikeyan.naraya...@gs.com wrote:
Hi,
We have installed the Solr in Tomcat server and enabled the
security constraint at the Tomcat level.. We require to pass the
authentication token(cookie) to the search call that is made
I think it could be as simple as if you have +1 entities in the param
that clean=false as well (because you are specifically interested in
just targeting that entity import) ...
- Jon
On Mar 15, 2009, at 3:07 AM, Shalin Shekhar Mangar wrote:
On Fri, Mar 13, 2009 at 9:56 PM, Jon Baer
Hi,
My experience is that the BQ parameter can be used with any query type.
You can define boosts on the query fields (qf) that are used with the
query terms (q) in your query, AND you can define additional boosts for
fields that are not used with the query terms through the bq or bf
parameters.
