I have used fq the way it is with dismax and it works fine.
fq is standard parameter and not specific to dismax.
So type:idea should work correctly.
-
Preetam
On Fri, Jul 18, 2008 at 11:30 AM, chris sleeman <[EMAIL PROTECTED]>
wrote:
> > btw, this *seems* to only work for me with standard search
I am not saying that fq parameter does not work with dismax.
I am saying that the way this query is written it wont work because the
dismax query handler would parse "type:idea" to a value "type idea" (without
the colon) which changes the query. This would be a problem whether you use
it in the ma
oops...my bad
please ignore the previous comment.
On Fri, Jul 18, 2008 at 6:07 PM, chris sleeman <[EMAIL PROTECTED]>
wrote:
> I am not saying that fq parameter does not work with dismax.
> I am saying that the way this query is written it wont work because the
> dismax query handler would p
: pretty huge issue. Everytime I run the snapinstaller, it requires that
: I restart jetty for the /admin/stats.jsp page to show items in the index
: (I assume searches would also fail, but haven't tried).
:
: Once I restart, no problem. Does anyone have a solution for this?
this message is a
: Is there an easy way to use fq to filter down but retain the overall facet
: query counts? I can't seem to find how to accomplish this but seems like a
: common item needed for navigating though a result set. I need to do this w/o
: holding a session and the counts always seem to reflect the c
: > Is really unique if we allow duplicates? I had similar
: > problem...
: >
:
: if you allowDups, then uniqueKey may not be unique...
allowDups is one of those features where Solr not only gives you enough
rope to hang yourself, but Solr also ties the rope into a knot, cust some
lumber, an
I recently migrated from standard solr server to multicore implementation. I
observed that wt=javabin is failing with this error
java.lang.RuntimeException: This is a binary writer , Cannot write to a
characterstream
at
org.apache.solr.request.BinaryResponseWriter.write(BinaryResponseWr
I found that in org.apache.solr.servlet.SolrServlet.java, always
PrintWriter object is sent as input parameter.
SolrServlet is deprecated.
If you are going to use new features like MultiCore, make sure you
have the XmlUpdateRequestHandler registered to /update
class="solr.XmlUpdateRequ