Failures in order/limit to get all

[olsonanl]

I'm trying to get all jobs using a large limit on the /job query. However, I get an error from the GET:

{"status":400,"data":null,"error":["Bad Request"]}

and find this in the logs:

[2014/10/31 16:22:12 CDT] [EROR] err too much data for sort() with no index
[2014/10/31 16:22:15 CDT] [EROR] err too much data for sort() with no index
[2014/10/31 16:22:18 CDT] [EROR] err too much data for sort() with no index
[2014/10/31 16:23:18 CDT] [EROR] err too much data for sort() with no index. add an index or specify a smaller limit
[2014/10/31 16:23:24 CDT] [EROR] err too much data for sort() with no index

Is this a configuration problem somewhere?

--bob

[wgerlach]

I just tried to look into this and saw that the default order "info.submittime" should already be indexed !? Wei or Jared, can you please take a look ? Bob, your request only included a limit, nothing else ?

[olsonanl]

I’ve tried with both limit and offset=0 and limit.

Was this a recent change? This server has been set up for a while.

—bob

On Oct 31, 2014, at 5:08 PM, Wolfgang Gerlach <notifications@github.commailto:notifications@github.com> wrote:

I just tried to look into this and saw that the default order "info.submittime" should already be indexed !? Wei or Jared, can you please take a look ? Bob, your request only included a limit, nothing else ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/329#issuecomment-61337953.

[wgerlach]

Yes, Jared added this only a few weeks ago:
b820370#diff-b1eea6e015c72608f00e6fa92b0609d5

I guess an update would fix your issue.

[teharrison]

this should be fixed, all sortable fields have been indexed