Table of contents
The EPFImporter is a command-line based tool, available to EPF partners, that allows for ingestion of the EPF-Relational files into a relational database. The tool is written in Python and the source code is available for modification by partners to fit their specific needs and platform. The zip file below contains documentation (also found below), an Installation document (also found below), three Python files, two json files, and a configuration file.
The following instructions are provided as a guideline to configuring a Mac computer running Mac OS X v10.6.x (Snow Leopard) for use with EPFImporter. Although EPFImporter is intended as a cross-platform tool, detailed instructions for configuring other systems for its use are outside the scope of this document. If you encounter issues with installation, please consult a system administrator who is familiar with your system configuration.
MySQL 5.1 or later
To verify that MySQL is installed, type:
To install MySQL:
1. Download the MySQL package for Mac OS X (32 or 64 bit, depending on your computer): http://dev.mysql.com/downloads/mysql/5.1.html#macosx-dmg.
2. Install everything in the package in this order: mysql, MySQLStartupItem, and (optional) MySQL preference pane.
This installs mysql into
3. Open MySQL.
Python 2.6 or later (already installed on Snow Leopard)
To verify that Python is installed, type:
To verify that the MySQLdb module is properly installed, type:
>>> import MySQLdb
To install MySQLdb:
1. Install the module using the instructions in the README that is included with the Python MySQLdb module download. Note that MySQL must be installed first; the module requires certain MySQL files to be present in order to configure itself properly.
2. Within the extracted tar file, edit site.cfg and make sure that mysql_config is pointing to the correct location. If you installed MySQL using the above instructions, you need to use this line:
mysql_config = /usr/local/mysql/bin/mysql_config
python setup.py build
sudo python setup.py install
To verify that everything is installed, type:
>>> import MySQLdb
For more information about this section, go to:
Immediately after install, your mysql database can be accessed by using user root and an empty password. If you’re using an existing mysql installation, you’ll need to use the appropriate user and password in the instructions below.
You may, instead of this step, put EPF data into an existing database. For more information, contact your database administrator.
To create an EPF database, type:
mysqladmin --user=root -p create epf
For more information about this section, go to:
The following lines create an “epfimporter” user with password “epf123” who has access to all tables in the “epf” database. Contact your database administrator if you need assistance.
To create an EPF database user, type:
mysql --user=root mysql -p
mysql> CREATE USER 'epfimporter'@'localhost' IDENTIFIED BY 'epf123';
mysql> GRANT ALL PRIVILEGES ON epf.* TO 'epfimporter'@'localhost' WITH GRANT OPTION;
mysql> CREATE USER 'epfimporter'@'%' IDENTIFIED BY 'epf123';
mysql> GRANT ALL PRIVILEGES ON epf.* TO 'epfimporter'@'%' WITH GRANT OPTION;
If you’re just getting started with mysql, the following may be helpful as well. Contact your database administrator if you need assistance.
mysql> CREATE USER 'admin'@'localhost';
mysql> GRANT RELOAD,PROCESS ON *.* TO 'admin'@'localhost';
EPF files are exported using the utf-8 character encoding. To maintain this encoding on import, the default character set in the database must be changed to utf-8.
To set the default character encoding to utf-8:
1. Connect to the epf database.
2. Run the following:
mysql> ALTER DATABASE DEFAULT CHARSET 'utf8';
To verify that the user privileges type:
mysql --user=epfimporter epf -p
mysql> show tables;
Empty set (0.00 sec)
Edit EPFConfig.json and EPFFlatConfig.json to correspond to the MySQL user that you have configured for EPFImporter.
For simplicity, the username and password used by EPFImporter to connect to the MySQL database are stored as plain text in the EPFConfigFull.json and EPFConfigIncremental.json files. Alternatively, they can be passed in as options on the command line, again in plain text.
The best security that can be provided under this implementation is to restrict access to the files themselves. A more thorough security model would depend on the needs of the user and the platform that EPFImporter is deployed on and is outside the scope of this sample code and documentation.
EPFImporter.py is executable from the command line and is the entry point for running EPFImporter. The other Python files (EPFIngester.py and EPFParser.py) must be present in the same directory but are not normally used directly.
EPFImporter also references certain configuration files (EPFConfig.json, EPFFlatConfig.json, EPFLogger.conf) that must also be in the same directory. These files can be edited by the user as needed. If they are removed or renamed, they are recreated with default values by EPFImporter the next time it is run.
Typing “./EPFImporter.py -h” at the command line (assuming you are in the same directory as EPFImporter.py) prints a usage and help description, including less-used options not described in this document.
To run EPFImporter, you must first have downloaded and uncompressed one or more EPF feeds. Once you have done so, simply run EPFImporter.py with a space-separated list of the uncompressed feed directories as arguments:
./EPFImporter.py /Users/EPF/Fulls/itunes20100423 /Users/EPF/Fulls/pricing20100423
Assuming the specified directories exist, the above causes EPFImporter to perform an import of the itunes and pricing feeds from 4/23/2010. No prior setup of the database is necessary; EPFImporter creates and configures all tables as needed based on the metadata in the EPF files.
EPFImporter automatically determines if each file is a Full or an Incremental export and performs the corresponding import type. Note that for an Incremental import to succeed, tables corresponding to the imported files must already exist in the database (normally from a previous Full import).
To import EPF Flat files, pass the -f flag. This causes EPFImporter to use values from EPFFlatConfig.json, corresponding to the different file format of the EPF Flat exports.
You can restrict which files are imported by using the -w (whitelist) and -b (blacklist) flags. The string following the flag is treated as a regular expression and is appended to a list of such expressions.
./EFImporter.py -w 'song' -b 'translation' /Users/EPF/Fulls/itunes20100423
The above imports all files containing “song” anywhere in the filename, except for those containing “translation”.
If a filename is matched by both the whitelist and blacklist, the blacklist always overrides, and the file is not imported.
To add more than one whitelist or blacklist string, pass multiple -w or -b options:
./EFImporter.py -w 'song' -w 'video' -b 'application' -b 'collection' /Users/EPF/Fulls/itunes20100423
Regular expressions can be very complex, containing many characters with special meanings. The special characters that are most commonly useful with EPF are the following:
|^||Matches the beginning of a string|
|$||Matches the end of a string|
|.||Matches any single character|
|*||Matches any number, including zero, of the preceding character|
Here are some examples of the above, including which files would be imported (or excluded, if in the blacklist) by EPFImporter:
|‘^song$’||only the exact file “song”|
|‘^song’||any file beginning with “song” (for example, song, song_mix, song_imix)|
|‘song$’||any file ending with “song” (for example, song, artist_song)|
|‘^song.*mix$ ‘||any file beginning with “song” and ending with “mix” (for example, song_mix, song_imix)|
If you want to restrict files for every import, you can do so by editing the whiteList and blackList lines in the appropriate EPFConfig.json or EPFFlatConfig.json file.
The progress of the last import is stored in EPFSnapshot.json. If an import is interrupted for any reason (for example, by a power outage), EPFImporter can use this file to automatically resume the import where it left off. To resume an import, simply pass the -r flag. No other arguments are needed:
EPFImporter resumes the import from the beginning of whichever file was interrupted and continues through the rest of the unimported files, respecting any -w and -b flags that were passed during the original run.
The output of EPFImporter is logged both to the console and to a file. When EPFImporter is first run, it creates an EPFLog directory. Each run creates a separate log file. The latest log is called EPFLog.log; when a new run is begun, the previous log is appended with a date-time stamp.
Logging options can be configured by editing the file EPFLogger.conf.
Because Full feeds contain a complete snapshot of the EPF data, Full imports are designed to import the new data and replace the old data as efficiently as possible.
For each file in a Full import, EPFImporter creates a new, temporary table in the database and populates it with the data in the file. When the import completes successfully, it renames the previous table (if it exists), then renames the new table to match the old one. Finally, it drops the old table from the database.
This process means that any access being made to the table at the moment the “swap” takes place will fail.
Incremental feeds contain data that has changed (or been added) since the last Full feed. Because Incremental imports must merge new data with existing data, they are more complex than Full imports.
Normally an Incremental import works by comparing the primary key of the row to be imported with the existing table. If no matching record exists, the new row is inserted; if a matching record is found, the new record replaces it.
Unfortunately, this process is inefficient for large files. Therefore, for Incremental files containing more than 500,000 records, EPFImporter uses a different method. This is similar to the Full import, but instead of replacing the old table, the old and new tables are merged into a third, temporary table via a complex union operation in the database. This table is then “swapped” with the existing table in the same manner as for a Full import.
Copyright © 2010 Apple Inc. All rights reserved.
IMPORTANT: This Apple software is supplied to you by Apple Inc. (“Apple”) in consideration of your agreement to the following terms, and your use, installation, modification or redistribution of this Apple software constitutes acceptance of these terms. If you do not agree with these terms, please do not use, install, modify or redistribute this Apple software.
In consideration of your agreement to abide by the following terms, and subject to these terms, Apple grants you a personal, non-exclusive license, under Apple’s copyrights in this original Apple software (the “Apple Software”), to use, reproduce, modify and redistribute the Apple Software, with or without modifications, in source and/or binary forms; provided that if you redistribute the Apple Software in its entirety and without modifications, you must retain this notice and the following text and disclaimers in all such redistributions of the Apple Software. Neither the name, trademarks, service marks or logos of Apple Inc. may be used to endorse or promote products derived from the Apple Software without specific prior written permission from Apple. Except as expressly stated in this notice, no other rights or licenses, express or implied, are granted by Apple herein, including but not limited to any patent rights that may be infringed by your derivative works or by other works in which the Apple Software may be incorporated.
The Apple Software is provided by Apple on an “AS IS” basis. APPLE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE OR IN COMBINATION WITH YOUR PRODUCTS.
IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER UNDER THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.