-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting capabilities in list entity operation [pending: orderBy=$near] #1103
Comments
Sorting by |
SOF answers that need to be edited when this issue gets completed: http://stackoverflow.com/questions/32703011/change-order-of-orion-response/32712248#32712248 |
Take into account talso sort by "nearest point". This PR may be useful: #1651. |
SOF answer that need to be edited when this issue gets completed: http://stackoverflow.com/questions/35172155/orion-context-broker-nearest-to-point-query |
Code implementation completed in PR #1815. However, let's keep this issue opened while doc for NGSIv2 get reviewed (and eventually updated) and the questions in SOF edited. |
At the end, the name of the URI parameter (to use in the documentation) is |
Doc modifications describing |
|
QA Acceptance Test pending. Reopened and asigned to QATestPending milestone. |
pending tests are created in its feature associated |
Issues in milestone QATestPendingNotE2ECovered are going to be closed (it is not realistic to think we would have people working on behave testing at the present moment). However, issue is labeled with QATestPending label in the case things change and we need to recover it. |
Eg:
http://broker.example.org/entities?type=Room&q=temperature<=22&sort=seatNumber
The parameter could be also used with a sequence of attributes, e.g
sort=seatNumber,temperature
. ASC and DESC order are specified with a+
(default) and-
prefix.sort=+seatNumber,-temperature
Feasibility assessment with Mongo shell: https://gist.github.com/fgalan/efd63ef261fa33d91784
The text was updated successfully, but these errors were encountered: