Project

General

Profile

Bug #3443

Rexpression actor, relation vs multiport and port type resolution

Added by Derik Barseghian about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Category:
actors
Target version:
Start date:
07/09/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3443

Description

Sending a dataframe from an R actor to a diamond-relation and then into multiple sinks can cause a typing error to do with the inputs ports of the sinks on first workflow run. One of the sinks will have its input port type set properly, but the rest will not, causing the workflow to fail. On subsequent runs it will work, however.

Additionally, if this R actor is outputting through a port with width 1 (non-multiport), it will behave as if it's a multiport, trying to send data out 4 channels (even though only 1 exists).

History

#1 Updated by Derik Barseghian about 11 years ago

Revision 7379 fixes this.
The setting of port types needed to be within a loop; it wasn't so it was only setting one sink port type.

Additionally, number of sinks was being used where output port width size should have been used -- e.g. a port that sends to a relation that sends to 4 sinks should just output on 1 channel, not 4. I don't think this was hurting anything, just causing confusion.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3443

Also available in: Atom PDF