You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Nguyễn Việt Đức (Jira)" <se...@james.apache.org> on 2020/09/14 07:18:00 UTC
[jira] [Updated] (JAMES-3374) Email/query Support sort by
ReceivedAt
[ https://issues.apache.org/jira/browse/JAMES-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nguyễn Việt Đức updated JAMES-3374:
-----------------------------------
Description:
# Why
For data sets where the total amount of data is expected to be very small, clients can just fetch the complete set of data and then do any sorting/filtering locally. However, for large data sets (e.g.,multi-gigabyte mailboxes), the client needs to be able to search/sort/window the data type on the server.
A query on the set of Foos in an account is made by calling "Foo/query".
This takes a number of arguments to determine which records to include, how they should be sorted, and which part of the result should be returned (the full list may be *very* long). The result is returned as a list of Foo ids.
# HOW
- Implement follow [RFC-8620][https://tools.ietf.org/html/rfc8620#section-5.5]
# DOD
- write an integration test demonstrating that the user can query/filter in both ascending and descending order.
was:
# Why
For data sets where the total amount of data is expected to be very small, clients can just fetch the complete set of data and then do any sorting/filtering locally. However, for large data sets (e.g.,multi-gigabyte mailboxes), the client needs to be able to search/sort/window the data type on the server.
A query on the set of Foos in an account is made by calling "Foo/query".
This takes a number of arguments to determine which records to include, how they should be sorted, and which part of the result should be returned (the full list may be *very* long). The result is returned as a list of Foo ids.
# HOW
- Implement follow [RFC-8620][https://tools.ietf.org/html/rfc8620#section-5.5]
{code}
# DOD
- write an integration test demonstrating that the user can query/filter in both ascending and descending order.
> Email/query Support sort by ReceivedAt
> --------------------------------------
>
> Key: JAMES-3374
> URL: https://issues.apache.org/jira/browse/JAMES-3374
> Project: James Server
> Issue Type: Improvement
> Reporter: Nguyễn Việt Đức
> Priority: Major
>
> # Why
> For data sets where the total amount of data is expected to be very small, clients can just fetch the complete set of data and then do any sorting/filtering locally. However, for large data sets (e.g.,multi-gigabyte mailboxes), the client needs to be able to search/sort/window the data type on the server.
> A query on the set of Foos in an account is made by calling "Foo/query".
> This takes a number of arguments to determine which records to include, how they should be sorted, and which part of the result should be returned (the full list may be *very* long). The result is returned as a list of Foo ids.
>
> # HOW
> - Implement follow [RFC-8620][https://tools.ietf.org/html/rfc8620#section-5.5]
> # DOD
> - write an integration test demonstrating that the user can query/filter in both ascending and descending order.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org