|
Unfortunately that still does not completely fix the problem. Module import and version import are then also broken.
Hrm - it appears that there are still exceptions:
Error importing data from bugzilla.java.sql.SQLException: We'll need to get some 2.17 data to test with. When will 2.6.2 or 2.7 be released?
Colin,
2.7 is still over a month away. However I've attached a version of the classes that should fix this bug in 2.6.1. The jar should be unpacked in the WEB-INF/classes directory (cd atlassian-jira/WEB-INF/classes ; 'jar xvf bugzillafix2.jar') to overwrite the old classes. --Jeff The patch you provided still falls down when importing versions.
Hmm - I have tested with a smallish 2.17 database and the patch works. If anyone experiencing problems with the patched classes could mail the stacktrace, or better yet, a MySQL dump of the Bugzilla database, that would be a big help.
There still seems to be a problem in component creation step.
In the log (I turned DEBUG on - but not a whole lot of extra info is printed): 2004-06-24 09:12:56,636 INFO [atlassian.jira.util.BugzillaImportBean] Importing Components from project(s) 'DealFX' 2004-06-24 09:12:56,636 INFO [atlassian.jira.util.BugzillaImportBean] Importing In the 'Bugzilla Import Progress' log window see the following: Importing project(s) 'DealFX' Importing Versions from project 'DealFX' [09:17:35] Importing Version: Future Importing Components from project(s) 'DealFX' [09:17:35] Importing Component: Atlantis I am also attaching the stack trace in the import window. nullpointer stack trace during import.
I am going against bz version 2.17.7 (obviously using patched classes)
also do you still need to have backward compatible columns fudged by hand? this is kinda bad - at least provide a sql script to perform the necessary updates.
Ilya,
Thanks for the stacktrace. In the meanwhile, the fastest solution may be to download JIRA 2.5.3 Standalone, and do the Bugzilla import with that. re. comment fudging: no, that should not be necessary with the patch.
Ok - good news - now import from 2.17.7 is working for me.
I realized that bugzilla import utility was checking the product table for existence of product column. I created this column in the 2.17.7 schema, in my early attempts to make schema look backward compatible. but because the update bugzilla import script was finding the 'product' column, 2.16 compatible importing was attempted - which would break. cheers. Import generally went ok, but when I imported a product that has many thousands of bugs, I got this error (repeatedly):
2004-06-24 09:22:52,908 INFO [atlassian.jira.util.BugzillaImportBean] 0 votes im Colin,
Those exceptions appear to be from the mail notification service running in the background, rather than from the Bugzilla importer's thread. As such, they are probably nothing to worry about. I've raised this as a separate bug though ( Ilya,
The stacktrace you attached indicates that the "create project" step failed, which later resulted in the "create components" step having failed. Did you run this against a clean JIRA database? Artifacts from previous failed imports could cause odd problems like this. For the record, I've successfully imported a 2700-issue test Bugzilla 2.17 database using this patch.
I have applied the patch and am still getting the stack trace Scott mentioned in his post above. Any suggestions? I noted the following message printed in the JIRA console window:
"[WARN] IteratorTag - -Value is null! Returning an empty set." The project is imported successfully, but I assume from the stacktrace it is failing when creating versions. Probably due to bad data, but would be helpful to know what data it was. java.sql.SQLException: Column not found, message from server: "Unknown column 'program' in 'where clause'" at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1977) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1163) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1272) at com.mysql.jdbc.Connection.execSQL(Connection.java:2236) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1555) at com.atlassian.jira.util.BugzillaImportBean.createVersions(BugzillaImportBean.java:568) at com.atlassian.jira.util.BugzillaImportBean.create(BugzillaImportBean.java:159) at com.atlassian.jira.web.action.util.BugzillaImport.doRun(BugzillaImport.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:415) at webwork.action.ActionSupport.execute(ActionSupport.java:144) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:49) Here are the SQL statements I had to run to get everything to import correctly. Note I was running Bugzilla 2.18.2, since I couldn't find a version of 2.17 to download from bugzilla.org, and had to migrate our old 2.12 system. Hopefully this helps someone. Everything imported successfully after this.
– Begin SQL - run in the Bugzilla MySQL database Peter,
Thanks for the note. I've raised a separate issue ( I'm using the standalone, evaluation version of JIRA. I originally had column name problems before patching with this bugzillafix2.jar. Now most of my databases import, but a few throw null pointer exceptions. Since I've patched with the provided jar, the publicly available BugzillaImportBean.java available in the Bugzilla importing documentation doesn't match the class files that I'm using. Can you post the new BugzillaImportBean source, so that I can debug my importing problems?
Thanks,
Vincent,
The source code for the Bugzilla importer is online at: http://www.atlassian.com/software/jira/docs/latest/importers/BugzillaImportBean.java |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Bugzilla importer: compatibility with 2.17 broken
Bugzilla changed its table format, in the product table 'name' and 'product' are the same.
If you do something like this, then the import should work. Please backup your data first.
ALTER TABLE products ADD COLUMN product CHAR(255);
UPDATE products SET product = name;
Then you should be able to import your data.