Opened 18 years ago

Closed 18 years ago

#318 closed defect (fixed)

Plugin configuration values are not stored for a job

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: BASE 2.1
Component: core Version: trunk
Keywords: Cc:


Consider the following case:

A user selects a plugin and configuration and creates a job, for example, for importing data. While the job is waiting in the job queue, an administrator changes to configuration. For example, the regular expressions used to parse a file. Now, when the job starts to execute it is possible that the selected file no longer can be parsed by the plugin and the import fails.

Another case is that you have done some analysis of data with certain configuration values. If the configuration is changed it may be that the analysed data no longer makes sense, but there is no way to tell what the original configuration values were.

The first case is annoying, but the second case could certainly be a major issue which may lead people to not trust data analysed by Base in all cases.

Change History (4)

comment:1 by Jari Häkkinen, 18 years ago

Milestone: BASE 2.x+BASE 2.1
Version: trunk

comment:2 by Nicklas Nordborg, 18 years ago

Priority: criticalmajor

comment:3 by Nicklas Nordborg, 18 years ago

Status: newassigned

comment:4 by Nicklas Nordborg, 18 years ago

Resolution: fixed
Status: assignedclosed

(In [2709]) Fixes #318: Plugin configuration values are not stored for a job

And updated some documentation as well.

Note: See TracTickets for help on using tickets.