Yeah, I edited it, and it works.
But now I face a new issue when importing users:
Importing users...
script/bulk_import/vbulletin.rb:363:in `strptime': invalid date (ArgumentError)
from script/bulk_import/vbulletin.rb:363:in `parse_birthday'
from script/bulk_import/vbulletin.rb:78:in `block in import_users'
from /var/www/discourse/script/bulk_import/base.rb:438:in `block (2 levels) in create_records'
from /usr/local/lib/ruby/gems/2.4.0/gems/rack-mini-profiler-0.10.5/lib/patches/db/mysql2.rb:6:in `each'
from /usr/local/lib/ruby/gems/2.4.0/gems/rack-mini-profiler-0.10.5/lib/patches/db/mysql2.rb:6:in `each'
from /var/www/discourse/script/bulk_import/base.rb:437:in `block in create_records'
from /usr/local/lib/ruby/gems/2.4.0/gems/pg-0.20.0/lib/pg/connection.rb:160:in `copy_data'
from /var/www/discourse/script/bulk_import/base.rb:436:in `create_records'
from /var/www/discourse/script/bulk_import/base.rb:178:in `create_users'
from script/bulk_import/vbulletin.rb:72:in `import_users'
from script/bulk_import/vbulletin.rb:25:in `execute'
from /var/www/discourse/script/bulk_import/base.rb:33:in `run'
from script/bulk_import/vbulletin.rb:377:in `<main>'
I know it’s the wrong date, but that what I get from users, I can’t check all dates manually and edit it.
The easiest way is that making parse_birthday function to check if the date is correct or not.
I wish I can develop on ruby; I try to learn it.
New issue :
After importing more than 200K users (I stop it by CTRL+C) I went to check out the imported users and sadly there are no inserted data in ‘discourse_development.users’ table.
Should it complete the importer to show up the users data or what?
Yup. The bulk importer works in “batches”. And by “batch” I mean “table by table”.
For speed, everything is kept in memory before it’s sent to the database.
Thank @zogstrip!
There are some problems with charset, some forums started from very early of vBulletin era, at that time, its charset was latin1. So the texts after importing are really messy.
How much ram do you have? You’ll need to have enough ram to hold the whole table. My guess is that you’re starting to swap and that’s slowing your down. Is swap on a hard drive or ssd?
Can it be “row by row”? Instead of “table by table”? And starts from where it ended (after last imported ID)?
This will be very helpful for large forums.
Hi guys, is there any need of mapping old forums (categories) into new configurable categories and tags? We can merge or split old categories into a new structure.
My idea is having .yml file that contains new categories and their old categories’ ids, including tags somehow.