Opened 17 years ago
Closed 17 years ago
#851 closed defect (fixed)
Migration doesn't transfer 'reportermap' wizzzard configurations
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.5 |
Component: | migrate | Version: | |
Keywords: | Cc: |
Description (last modified by )
From the mailing list by Pawel Sztromwasser: http://www.mail-archive.com/basedb-users@lists.sourceforge.net/msg00962.html
The wizzard transfer works like this (when comes to mapping):
- it parses mapping string from Base1 database using regular expression looking for (key:value) pairs separated by comma. Example part of a mapping string:
_r_block:1,_r_x:\"Column"\,_r_y:\"Row"\,reporterId:\"Probe_ID"\,
- it puts the (key,value) pairs into HashMap
- and uses this map when configuring import plugin. When getting those values, it looks for certain keys ('numCol' and 'numRow' are among them, explicitly coded around lines 130 and 140 in WizzzardTransfer.java). When there is no value in HashMap it returns null, so null is passed to plugin configuration. Then it complains:
10:58:47,690 DEBUG WizzzardTransfer:281 - Setting parameter values for a reportermap-FormatType 10:58:47,690 DEBUG WizzzardTransfer:314 - net.sf.basedb.core.InvalidUseOfNullException: Invalid use of null. The 'columnColumnMapping' value cannot be set to null. 10:58:47,690 DEBUG WizzzardTransfer:314 - net.sf.basedb.core.InvalidUseOfNullException: Invalid use of null. The 'rowColumnMapping' value cannot be set to null. 10:58:47,690 WARN WizzzardTransfer:321 - The wizzard [11:Agilent test map format w/o block] could not be transfered
Change History (4)
comment:1 by , 17 years ago
Description: | modified (diff) |
---|
comment:2 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 17 years ago
There is also a problem with complex column mappings. BASE 2 no longer accepts complex mappings by default. The parameter "complexExpressions" must be set to "allow".
comment:4 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
BASE 1 seems to define three column mappings for this importer that are important in this case. Here is the list and the corresponding plug-in parameters for the BASE 2 importer
As for the other importers, all reporter column mappings except for the 'reporterId' should be ignored. Meta grid X/Y column mappings that are available in BASE 2 didn't exist in BASE 1 and should also be ignored.