Thanks Show and Hoss.
Just added lowercaseOperators=false to my edismax config and everything
seems to be working.
*Thanks,*
*Rajesh,*
*(mobile) : 8328789519.*
On Mon, Apr 27, 2015 at 11:53 AM, Rajesh Hazari
wrote:
> I did go through the documentation of edismax (solr 5.1 documentation),
> that
I did go through the documentation of edismax (solr 5.1 documentation),
that suggests to use "*stopwords"* query param that signal the parser to
respect stopfilterfactory while parsing, still i did not find this is
happening.
my final query looks like this
http://host/solr/collection/select?q=ter
Thank you Hoss from correcting my understanding, again i missed this
concept of edismax.
Do we have any solrj class or helper to handle the scenario to pass on the
query terms (by stripping stopwords ) to edismax using solrj api.
for ex: if user queries for *"term1 and term2"* build and query to p
: I was under understanding that stopwords are filtered even before being
: parsed by search handler, i do have the filter in collection schema to
: filter stopwords and the analysis shows that this stopword is filtered
Generally speaking, your understanding of the order of operations for
query
On 4/24/2015 10:55 AM, Rajesh Hazari wrote:
> I was under understanding that stopwords are filtered even before
> being parsed by search handler, i do have the filter in collection
> schema to filter stopwords and the analysis shows that this stopword
> is filtered
>
> Analysis response : attached
I was under understanding that stopwords are filtered even before being
parsed by search handler, i do have the filter in collection schema to
filter stopwords and the analysis shows that this stopword is filtered
Analysis response : attached is the solr analysis json response.
[image: Inline im
: And stopword in user query is being changed to q.op=AND, i am going to
: look more into this
This is an explicitly documented feature of the edismax parser...
https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser
* treats "and" and "or" as "AND" and "OR" in Lucene
Hi All,
And stopword in user query is being changed to q.op=AND, i am going to
look more into this
i thought of sharing this in solr community just in-case if someone have
came across this issue.
OR
I will also be validating my config and schema if i am doing something
wrong.
solr : 4.9
query pa
