On 07/18/2012 02:39 PM, Richard Frovarp wrote:
On 07/18/2012 11:20 AM, Erick Erickson wrote:
the ~2 is the mm parameter I'm pretty sure. So I'd guess your
configuration has
a mm parameter set on the core that isn't doing what you want..
I'm not setting the mm parameter or the q.op paramet
On 07/18/2012 11:20 AM, Erick Erickson wrote:
the ~2 is the mm parameter I'm pretty sure. So I'd guess your configuration has
a mm parameter set on the core that isn't doing what you want..
I'm not setting the mm parameter or the q.op parameter. All three cores
have a defaultOperator of O
the ~2 is the mm parameter I'm pretty sure. So I'd guess your configuration has
a mm parameter set on the core that isn't doing what you want..
Best
Erick
On Tue, Jul 17, 2012 at 3:05 PM, Richard Frovarp wrote:
> On 07/14/2012 05:32 PM, Erick Erickson wrote:
>>
>> Really hard to say. Try exe
On 07/14/2012 05:32 PM, Erick Erickson wrote:
Really hard to say. Try executing your query on the cores with
&debugQuery=on and compare the parsed results (for this you
can probably just ignore the explain bits of the output, concentrate
on the parsed query).
Okay, for the example core from th
Really hard to say. Try executing your query on the cores with
&debugQuery=on and compare the parsed results (for this you
can probably just ignore the explain bits of the output, concentrate
on the parsed query).
Best
Erick
On Fri, Jul 13, 2012 at 11:25 AM, Richard Frovarp wrote:
> I'm having t
I'm having trouble with edismax not working in one of my cores. I have
three cores up and running, including the demo in Solr 3.6 on Tomcat
7.0.27 on Java 1.6.
I can't get edismax to work on one of those cores, and it's configured
very similar to the demo, which does work. I have different fie
