Closed dmanners closed 6 years ago
I have some open questions on this solution I would like to get people's thoughts on.
There are two approaches here either replace the usage of CollectionByPagesIteratorFactory
inside this class or try to get the iterator to work without making objects. I picked to replace the usage here as the iterator is used in not just the customer import but other import processes, though that does mean this problem can happen in multiple places. Should we fix or replace?
The current Storage class allows you to init it with a page size. My current changes ignores this and just loads all the customers. I am not too sure in what cases page size is setup but it maybe that we find some cases that only load a limited set of customers during import or export.
Also I am still working on the tests but I thought I would get people's thoughts first.
@dmanners thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.
Description
With the following settings a customer import would crash with an out of memory problem.
Fixed Issues (if relevant)
Manual testing scenarios
Contribution checklist