: We did notice on thing that appears incorrect. The sort mechanism being
: performed by the client adds a request parameter before sending to
: lucene.
:
: /solr/select?q=term&sort=name+asc
...
: According to lucene docs
: (http://incubator.apache.org/solr/tutorial.html#Sorting), the sort
: '''should be''' appended after the query term:
:
: /solr/select?q=term;name+asc
this is one of those situations where RequestHandlers deviat -- the
StandardRequestHandler expects any sort to be specified with a ; after the
query string -- the DisMaxRequestHandler uses a seperate paramater -- a
quick grep of the code from SOLR-30 seems to indicate that functionality
is exposed in that API as "_dismaxSort" so the usage seems appropraite.
this is one of the hard things to get right about a client API for Solr --
the request handler plugin approach makes the scope of legal requests
almost as large as the scope of legal HTTP requests -- so designing an API
that is general enough to use with more then one request handler, but
still adds value beyond just using an HTTP client library directly is a
delicate blanace.
-Hoss
