Explaining Bunches
The Pacemaker is able to handle Bunches.
In general, this functionality will only make sense in a multithreaded or multiprocessing environment where the bunches can be imported in parallel.
In this case, it should only give the developer an idea of how a multiprocess functionality can be implemented.
|
A bunch is a CSV file, which is only a part of a complete import |
-
It does not matter what kind of data a bunch contains, as the importer handles the data in the necessary order
-
The first step is to import all simple products found in a bunch
-
After that, information such as the created entity IDs is released in connection with the imported SKUs, which are necessary to import all other product data (bunches, configurables, images, related, etc.).
-
It is possible to import this data step by step, but each step also in parallel.
Split an import into multiple bunches; the bundled files MUST follow the following pattern:
-
The prefix has to equal, e.g.
product-import -
The prefix has to be followed by an underscore (
_) -
A random number of alphanumeric characters has to follow.
-
These characters have also to be followed by an underscore (
_) -
Finally, each bunch must have a sequential number, followed by a
.csv
For example, the following CSV files that contain the product sample data will be imported as a bunch:
-
var/importexport/product-import_20170203-1234_01.csv -
var/importexport/product-import_20170203-1234_02.csv -
var/importexport/product-import_20170203-1234_03.csv -
var/importexport/product-import_20170203-1234_04.csv
When starting the import process by invoking the appropriate command, those files will be imported as one file.
|
It is not necessary to gather the importer four times |