The problem has existed since 5.2 and would potentially affect loading any earlier version.
Prior to 5.2 the object model used by the guided decision table did not hold a Pattern to which individual condition columns are bound.
The conversion code groups individual condition columns into the appropriate group and moves the underlying column data accordingly (as there was no guarantee columns with the same bound name were consecutive).
There was a problem with the creation and insertion of the new Pattern objects that relied upon the order of entries in a HashMap being consistent. This has now changed.
I know others have been using the new guided decision table with old repositories without problem and our unit tests did not detect the problem either.
AFAIK this is the first report of any such issue since the release of 5.2's betas, however I would be wrong to say there is no risk.
sent on the move
does this issue happen for any previous version of Guvnor data such as 5.0
or 5.1 or 5.2 exported and imported into a Guvnor 5.3 repository ?
does this mean, we cannot rely on 5.3.0 version of Guvnor code when
migrating data from a previous version and should rather apply the fix ?
--
View this message in context: http://drools.46999.n3.nabble.com/rules-users-Migrating-repository-data-from-Drools-5-0-to-5-3Final-tp3715772p3724570.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users