You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Bernd Fehling <be...@uni-bielefeld.de> on 2011/04/13 15:57:02 UTC

strange behavior of echoParams

Dear list,

after setting "echoParams" to "none" wildcard search isn't working.
Only if I set "echoParams" to "explicit" then wildcard is possible.

http://wiki.apache.org/solr/CoreQueryParameters
states that "echoParams" is for debugging purposes.

We use Solr 3.1.0.

Snippet from solrconfig.xml:
<requestHandler name="standard" class="solr.SearchHandler" default="true">
      <lst name="defaults">
        <str name="echoParams">none</str>
<!--       <str name="echoParams">explicit</str> -->
        <str name="wt">xml</str>
        <int name="rows">10</int>
      </lst>
</requestHandler>

Any explanation about this behavior?

Regards,
Bernd

Re: strange behavior of echoParams

Posted by Bernd Fehling <be...@uni-bielefeld.de>.
Hi Erik,

never mind.
Can't reproduce this strange behavior.
Obviously stopping and starting of solr solved this.

Thanks,
Bernd


Am 13.04.2011 16:00, schrieb Erik Hatcher:
> What does the parsed query look like with debugQuery=true for both scenarios?
> Any difference?
> Doesn't make any sense that echoParams would have an effect, unless somehow your search client is relying on parameters returned to do something with them.?!
>
> 	Erik
>
> On Apr 13, 2011, at 09:57 , Bernd Fehling wrote:
>
>> Dear list,
>>
>> after setting "echoParams" to "none" wildcard search isn't working.
>> Only if I set "echoParams" to "explicit" then wildcard is possible.
>>
>> http://wiki.apache.org/solr/CoreQueryParameters
>> states that "echoParams" is for debugging purposes.
>>
>> We use Solr 3.1.0.
>>
>> Snippet from solrconfig.xml:
>> <requestHandler name="standard" class="solr.SearchHandler" default="true">
>>      <lst name="defaults">
>>        <str name="echoParams">none</str>
>> <!--<str name="echoParams">explicit</str>  -->
>>        <str name="wt">xml</str>
>>        <int name="rows">10</int>
>>      </lst>
>> </requestHandler>
>>
>> Any explanation about this behavior?
>>
>> Regards,
>> Bernd
>


Re: phpnative response writer in SOLR 3.1 ?

Posted by Chris Hostetter <ho...@fucit.org>.
: Subject: phpnative response writer in SOLR 3.1 ?
: References:
:     <15...@uni-bielefeld.de>
:  <0D...@gmail.com>
: In-Reply-To: <0D...@gmail.com>

http://people.apache.org/~hossman/#threadhijack
Thread Hijacking on Mailing Lists

When starting a new discussion on a mailing list, please do not reply to 
an existing message, instead start a fresh email.  Even if you change the 
subject line of your email, other mail headers still track which thread 
you replied to and your question is "hidden" in that thread and gets less 
attention.   It makes following discussions in the mailing list archives 
particularly difficult.



-Hoss

phpnative response writer in SOLR 3.1 ?

Posted by Ralf Kraus <rk...@pixelhouse.de>.
Hello,

I just updatet to SOLR 3.1 and wondering if the phpnative response 
writer plugin is part of it?
( https://issues.apache.org/jira/browse/SOLR-1967 )

When I try to compile the sources files I get some errors :

PHPNativeResponseWriter.java:57: 
org.apache.solr.request.PHPNativeResponseWriter is not abstract and does 
not override abstract method 
getContentType(org.apache.solr.request.SolrQueryRequest,org.apache.solr.response.SolrQueryResponse) 
in org.apache.solr.response.QueryResponseWriter
public class PHPNativeResponseWriter implements QueryResponseWriter {
        ^
PHPNativeResponseWriter.java:70: method does not override a method from 
its superclass
         @Override
          ^

Is there a new JAR File or something I could use with SOLR 3.1? Because 
the SOLR pecl Package only uses XML oder PHPNATIVE as response writer ( 
http://pecl.php.net/package/solr )

-- 
Greetings,

Ralf Kraus


Re: strange behavior of echoParams

Posted by Erik Hatcher <er...@gmail.com>.
What does the parsed query look like with debugQuery=true for both scenarios?  Any difference?  Doesn't make any sense that echoParams would have an effect, unless somehow your search client is relying on parameters returned to do something with them.?!

	Erik

On Apr 13, 2011, at 09:57 , Bernd Fehling wrote:

> Dear list,
> 
> after setting "echoParams" to "none" wildcard search isn't working.
> Only if I set "echoParams" to "explicit" then wildcard is possible.
> 
> http://wiki.apache.org/solr/CoreQueryParameters
> states that "echoParams" is for debugging purposes.
> 
> We use Solr 3.1.0.
> 
> Snippet from solrconfig.xml:
> <requestHandler name="standard" class="solr.SearchHandler" default="true">
>     <lst name="defaults">
>       <str name="echoParams">none</str>
> <!--       <str name="echoParams">explicit</str> -->
>       <str name="wt">xml</str>
>       <int name="rows">10</int>
>     </lst>
> </requestHandler>
> 
> Any explanation about this behavior?
> 
> Regards,
> Bernd