You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
should send an error:
filters: allInThreadHaveKeyword/someInThreadHaveKeyword/noneInThreadHaveKeyword
sorting: allInThreadHaveKeyword/someInThreadHaveKeyword
collapseThreads
(and more generically any other unsupported value)
it seems that CalculateTotal can't be implemented with reasonable performance with elastic search #3730 so research with negative position is not possible too : #3733
update documentation to show the status of our implementation #3741
Make sure to test querying while using back reference. It should pose problem due to the async nature of the elastic search indexing.
The text was updated successfully, but these errors were encountered:
Epic ticket to prioritize Email/query tickets
Email/query
1. Email/query without parameters
1.1 Response: all emails from account #3706
1.2 When capabitility "shares": all emails from account + all emails from shared mailboxes #3717
2. Filters
2.1 inMailbox + inMailboxOtherThan handling + implicit AND #3714
2.2 Combination of filters (AND, OR, NOT) #3725
2.3 date #3727
2.4 size #3718
2.5 keywords (has/not) #3719
2.6 hasAttachments #3721
2.7 from/to/cc/bcc/subject #3734
2.8 body #3736
2.9 text #3735
2.10 header #3737
3. Sort
3.1 receivedDate #3712
3.2 expose allowed sort in accountCapabilities #3728
3.2 sentAt #3713
3.3 size/from/to/subject #3742
3.4 hasKeyword #3743
3.5 expose supported collation in session capabilities object #3744
4. Limits #3729
5. CalculateTotal #3730
6. Pagination
6.1 Position #3731
6.2 Negative position #3732
6.3 Position with limit #3733
6.3 Anchor / AnchorOffset
6.4 Negative anchorOffset
7. Unsupported #3738
filters: allInThreadHaveKeyword/someInThreadHaveKeyword/noneInThreadHaveKeyword
sorting: allInThreadHaveKeyword/someInThreadHaveKeyword
collapseThreads
(and more generically any other unsupported value)
it seems that CalculateTotal can't be implemented with reasonable performance with elastic search #3730 so research with negative position is not possible too : #3733
update documentation to show the status of our implementation #3741
Make sure to test querying while using back reference. It should pose problem due to the async nature of the elastic search indexing.
The text was updated successfully, but these errors were encountered: