Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#1159 closed defect (fixed)

Annotation importer should detect non-existing column mappings

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: trivial Milestone: BASE 2.9
Component: coreplugins Version:
Keywords: Cc:

Description

The detection should be done in the job configuration phase and displayed for the user so it can be corrected. Right now it is possible to enter \foo\ as the mapping for Name and the error message doesn't appear until the job is executed:

net.sf.basedb.core.BaseException: Column 'foo' not found in column headers.
at net.sf.basedb.util.parser.FlatFileParser.getMapper(FlatFileParser.java:968)
at net.sf.basedb.util.parser.FlatFileParser.getMapper(FlatFileParser.java:874)
at net.sf.basedb.plugins.AbstractFlatFileImporter.getMapper(AbstractFlatFileImporter.java:1236)
at net.sf.basedb.plugins.AnnotationFlatFileImporter.beginData(AnnotationFlatFileImporter.java:697)
at net.sf.basedb.plugins.AbstractFlatFileImporter.doImport(AbstractFlatFileImporter.java:691)
at net.sf.basedb.plugins.AbstractFlatFileImporter.run(AbstractFlatFileImporter.java:468)
at net.sf.basedb.core.PluginExecutionRequest.invoke(PluginExecutionRequest.java:106)
at net.sf.basedb.core.InternalJobQueue$JobRunner.run(InternalJobQueue.java:504)
at java.lang.Thread.run(Thread.java:619)

Change History (3)

comment:1 by Nicklas Nordborg, 15 years ago

Owner: changed from everyone to Nicklas Nordborg
Status: newassigned

comment:2 by Nicklas Nordborg, 15 years ago

Resolution: fixed
Status: assignedclosed

(In [4614]) Fixes #1159: Annotation importer should detect non-existing column mappings

comment:3 by Nicklas Nordborg, 15 years ago

(In [4615]) References #1159: Annotation importer should detect non-existing column mappings

Removed debug output.

Note: See TracTickets for help on using tickets.