Difference between revisions of "Importer Testing"

Revision as of 02:36, 14 February 2009

braindump = on

Testing the importer is straightforward. First, make sure your database is up to date and all of your code is checked out, etc. Now, try to do this:

# schedule an import
bin/test/schedule-import -u xb95 -p SOMEPASSWORD -t xb95_on_dw -s livejournal.com

That schedules an import task for user xb95 on site livejournal.com with the given password. It will import the data to the target xb95_on_dw. Huzzah.

Now you need to fire up (and keep this running) the scheduler:

# keep scheduler running foreground, and watch the log
bin/import-scheduler --foreground &
tail -f logs/import-scheduler.log

With that running in one window you should see some noise that says it's scheduling jobs. Woot! That's good. But now you need to have the jobs that actually get stuff done.

# start TheSchwartz worker manually
bin/worker/content-importer

You will see any noise that happens. Warnings/STDERR output will be dumped to the console. (Which generally means we need to have better debugging output for the importer, sending to STDERR in what is supposed to be a daemon is not really going to be that useful...)

braindump = off