You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/08/07 14:58:45 UTC
[GitHub] wohali opened a new issue #1511: Support arbitrary result sorting
in views and/or mango
wohali opened a new issue #1511: Support arbitrary result sorting in views and/or mango
URL: https://github.com/apache/couchdb/issues/1511
@davisp:
> We have sorting. Though I'm assuming you mean sorting any result set based on some selected field. This makes me squeamish for similar reasons to JOINS in that the resource usage is unbounded and also involves a significant increase in complexity vs what I'm not sure would lead to equivalent gains in usefulness.
>
>For reference, this is from the MongoDB docs on sorting limits [1]:
>
>"If MongoDB cannot use an index to get documents in the requested sort order, the combined size of all documents in the sort operation, plus a small overhead, must be less than 32 megabytes."
>
>So basically, a query will work until it suddenly doesn't if your data set happens to exceed 32MiB. Obviously you wouldn't want to just not cap the memory usage here as a bad query could OOM your server. And I swear that value used to be 4MiB and has since been bumped because I assume people kept getting angry that their queries would seem to randomly failed after their app had been used a while.
>
>[1] https://docs.mongodb.com/manual/reference/limits/#Sort-Operations
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services