Menu

#1 LocalSolrQureyComponent use defType and related params

open
nobody
None
5
2009-05-03
2009-05-03
Anonymous
No

the LocalSolrQureyComponent currently ignores
any user-specified defType (i.e dismax), as well as
always defaults to using the standard lucene QParser
rather than any solr custom one. This prevents among other things
some common solr parameters (like mm - minimum match) from working.
This patch fixes this issue.
I've been using this version for some time and seems stable, also in regards
to sorting.

-Kaktu Chakarabati

Discussion

  • Nobody/Anonymous

    LocalSolrQureyComponent.java diff file

     
  • Nobody/Anonymous

    A note:
    In some cases it is desired to simply find all items in index
    in given distance radius from a certain point.
    To this end, we can still use the dismax request parser
    by using a query such as:
    .../?qt=geo&lat=..&long=..&radius=..&q=&q.alt=*:*

    -Chak

     
  • Anonymous

    Anonymous - 2010-03-11

    This seems great and I'm wondering why this is not part of the core project already. I'm using the latest LocalSolr from the trunk so unfortunately this patch can no longer be applied as I get a bunch of conflicts (and I'm not a java programmer so I'm not going to try to merge).

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.