0

As per the documentation.

However, it doesn't actually appear to be the case. For example, here is a list of order_id properties I sent to the log while iterating through a list of ScoredDocuments returned by a search query:

62083050
62083026
62083044
62083032
62083043
62083057
62083055
62083013
62083049
62083047

I am using SDK 1.7.3.

Martijn Pieters
  • 1,048,767
  • 296
  • 4,058
  • 3,343
HorseloverFat
  • 3,290
  • 5
  • 22
  • 32
  • as per the docs: "If not specified, the number of seconds since 1st Jan 2011 is used" sooooo that may be your case? – Samuele Mattiuzzo Dec 19 '12 at 13:47
  • right. I see. order_id is something the user specifies when he/her puts a document in the index. thanks. – HorseloverFat Dec 19 '12 at 13:51
  • but, I still don't understand why they're not sorted. "If not specified, the number of seconds since 1st Jan 2011 is used". 'Used' presumably means, 'used for the order_id'.Then it says "Documents are returned in descending order of the order ID." So the list in my question should be sorted in descending order, no? – HorseloverFat Dec 19 '12 at 14:05
  • they use, per default, the number of seconds passed from 1st jan 2k11 to the datetime of the post --> they basically sort them on posting time, descending order... OR you specify your order_id and so on – Samuele Mattiuzzo Dec 19 '12 at 14:08
  • yes, that's how I understand it should work. but it isn't actually sorted in descending order when I iterate through some results. – HorseloverFat Dec 19 '12 at 14:10

0 Answers0