: Just to make sure I interpret the results correctly:
: - they all have a score of 1.7046129
: - the order they are presented in is therefore not related to the score,
: it is just the order in which the data is internally stored (like an SQL
: SELECT statement without ORDER BY clause)
The order they are presented *is* related to the score -- but since the
scores are all identical, and no secondary sort is specified, the behavior
is undefined -- and can varry depending on the replica used.
: - If I want to force a sort operation, I should add a sort parameter
: in the query. The first sort will be done by score and then documents
: with the same score will be sorted by my sort=?? paremeter?
: - or will my sort parameter overwrite the score sorting?
if you specify a sort param, it should be the full sort you want -- it
won't be "appended" to the default score sort ... so if, for example, you
wanted to sort by score, with a secondary fallback sort by your "id"
field, use something like...
sort=score desc, id asc
-Hoss
http://www.lucidworks.com/
