[EXTDAM-345] S3 API does not allow ordering results Created: 24/Feb/22 Updated: 25/Mar/22 Resolved: 23/Mar/22 |
|
| Status: | Closed |
| Project: | External DAMs |
| Component/s: | s3 |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | 1.1.4 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Jesus Alonso | Assignee: | Yen Lac Tue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | VN-Implementation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2d 10m | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Epic Link: | Extdam Later | ||||||||
| Sprint: | AuthorX 5 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
The S3 asset list is obtained retrieving different pages. The S3 list API lets you specify how many items and from where key you want to retrieve items. However, it does not allow specifying the order. So now, when we order the S3 list, we obtain a page in natural order and then order that particular page. Unfortunately, as the pages are not ordered, this doesn't work well in case of having several pages in your list. We can see it in this example -> Screen Recording 2022-02-24 at 12.09.34.mov So we have to remove the option to order s3 assets.
|