[ECOMMERCE-590] Improve pagination on the commercetools connection calls Created: 01/Sep/23  Updated: 30/Nov/23

Status: Open
Project: E-commerce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Andrei Ichimescu Assignee: ricardo gonzalez
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones ECOMMERCE-589 External eCommerce search suppliers s... Open
dependency
depends upon ECOMMERCE-543 Commerce tools: queries search only w... Closed
relation
is related to ECOMMERCE-587 The timeouts values for e-commerce co... Closed
is related to ECOMMERCE-543 Commerce tools: queries search only w... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: AuthorX Maintenance
Story Points: 3
Team: AuthorX

 Description   

All e-commerce connectors are affected, BUT this ticket addresses the highest criticality user case, hence Pagination for commercetools only

Acceptance criteria

  1. Apply limit & offset when calling the commercetools sdk, as opposed to doing it in memory

Development notes  

When we talk about Pagination we have three areas to cover:

  • Products
  • Categories
  • Results Search supplier 

Some interfaces might be changed, please ensure the backwards compatibility is being kept.

Slack conversation: https://magnolia-cms.slack.com/archives/CDQMBJVV1/p1687955555000469

Connection timeout: https://git.magnolia-cms.com/projects/ADDON/repos/ecommerce/browse/magnolia-ecommerce-salesforce-connector/src/main/java/info/magnolia/ecommerce/salesforce/client/SalesforceHttpClient.java#63

Sync with ECOMMERCE-589 when applying the pagination on the search suppliers


Generated at Mon Feb 12 01:45:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.