Project

General

Profile

Actions

Bug #18341

closed

API sort hash is not working, but sort_by and sort_order are working but undocumented

Added by Tomáš Strachota about 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
API
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1138262

Description of problem:
In the API the order option is working. The documented sort hash is not working. There are undocumented sort_by and sort_order that are working instead.

Not working sort hash:

# curl -K /opt/hoici/etc/curl-admin.conf -H 'Content-Type: application/json' -d '{"per_page":"9999","sort":{"by":"name","order":"desc"}}' -XGET https://localhost/katello/api/v2/organizations/4/products | jq . | tail -n10
  "sort": {
    "order": null,
    "by": null
  },
  "search": null,
  "per_page": "9999",
  "page": 1,
  "subtotal": 19,
  "total": 19
}

Working order:

# curl -K /opt/hoici/etc/curl-admin.conf -H 'Content-Type: application/json' -d '{"per_page":"9999","order":"name desc"}' -XGET https://localhost/katello/api/v2/organizations/4/products | jq . | tail -n10
  "sort": {
    "order": "desc",
    "by": "name" 
  },
  "search": null,
  "per_page": "9999",
  "page": 1,
  "subtotal": 19,
  "total": 19
}

Working sort_by and sort_order:

# curl -K /opt/hoici/etc/curl-admin.conf -H 'Content-Type: application/json' -d '{"per_page":"9999","sort_by":"name","sort_order":"desc"}' -XGET https://localhost/katello/api/v2/organizations/4/products | jq . | tail -n 10
  "sort": {
    "order": "desc",
    "by": "name" 
  },
  "search": null,
  "per_page": "9999",
  "page": 1,
  "subtotal": 19,
  "total": 19
}

Expected results:
Consistent API functionality and documentation for sorting the results


Related issues 1 (0 open1 closed)

Blocks Hammer CLI - Bug #18340: Hammer params for ordering are inconsistentClosedOleh FedorenkoActions
Actions #1

Updated by Tomáš Strachota about 7 years ago

  • Blocks Bug #18340: Hammer params for ordering are inconsistent added
Actions #2

Updated by Justin Sherrill about 7 years ago

  • Subject changed from API sort hash is not working, but sort_by and sort_order are working but undocumented to API sort hash is not working, but sort_by and sort_order are working but undocumented
  • Category set to API
  • translation missing: en.field_release set to 114
Actions #3

Updated by Tomáš Strachota over 6 years ago

Ideally we unify the parameters with 'order' and 'by' that foreman uses today.
The steps should be:
  • document the params correctly in the API of Katello
  • fix the systems to use only one set of params for ordering (backward compatibility needs to be kept)
  • add deprecation warnings when the old params are used
Actions #4

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7707 added
Actions #5

Updated by Oleh Fedorenko over 5 years ago

  • Assignee deleted (Bryan Kearney)

Assigned to Oleh Fedorenko (https://projects.theforeman.org/users/9990)

Also the description is not quite correct.

Working order actually:

# curl -K /opt/hoici/etc/curl-admin.conf -H 'Content-Type: application/json' -d '{"per_page":"9999","order":"name desc"}' -XGET https://localhost/katello/api/v2/organizations/4/products | jq . | tail -n10
  "sort": {
    "order": "desc",
    "by": "name" 
  },
  "search": null,
  "per_page": "9999",
  "page": 1,
  "subtotal": 19,
  "total": 19
}

and not working sort hash:

# curl -K /opt/hoici/etc/curl-admin.conf -H 'Content-Type: application/json' -d '{"per_page":"9999","sort":{"by":"name","order":"desc"}}' -XGET https://localhost/katello/api/v2/organizations/4/products | jq . | tail -n10
  "sort": {
    "order": null,
    "by": null
  },
  "search": null,
  "per_page": "9999",
  "page": 1,
  "subtotal": 19,
  "total": 19
}

Actions #6

Updated by Tomáš Strachota over 5 years ago

  • Description updated (diff)

I mixed section headings when I was reporting the bug. Sorry for that, it's fixed now.

Actions #7

Updated by Oleh Fedorenko over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF