#1212: Allow transformer without direct 'requirement' to consume records from
multiple indirect requirements
---------------------------+-----------------------------
Reporter: kasper | Owner:
Type: enhancement | Status: new
Priority: very high | Milestone: DataCleaner X.0
Component: AnalyzerBeans | Keywords:
---------------------------+-----------------------------
Influenced classes:
---------------------------+-----------------------------
Right now we have a very strict mode of evaluating whether a transformer
(or other component) can consume a row: Only if all of it's dependencies
are satisfied for execution.
But if a transformer consumes records from multiple other component, which
have opposite requirements, it will always end in NO records are
consumeable. In such cases we should allow execution, not disallow it.
--
Ticket URL: <http://eobjects.org/trac/ticket/1212>
eobjects <http://eobjects.org/trac>
The eobjects project management system, based on the trac system.
--
You received this message because you are subscribed to the Google Groups
"DataCleaner-notify" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/datacleaner-notify.
For more options, visit https://groups.google.com/groups/opt_out.
