Project

General

Profile

Actions
Copy link

Bug #2357

closed

EML2DataSource connection problem (asColumnBasedRecord)

Added by Dan Higgins almost 19 years ago. Updated almost 19 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jing Tao
Category:
data access
Target version:
1.0.0beta1
Start date:
02/15/2006
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2357

Description

When an EML2DataSource is configured as to retrun the data as a
'ColumnBasedRecord' it can be connected to an RExpression actor to create an R
dataframe and the workflow executes OK; However, if the workflow is saved and
then re-opened, the connection between the datasource and the RExpression actor
is no longer present. i.e. the workflow will not 'remember' the connection!

see workflows/R/eml_Table_as_Record_R.xml example

Actions
Copy link
 #1

Updated by Jing Tao almost 19 years ago

The disconection issue came from the eml datasource constructor. If the
initialize output type is as same as the real outtype, the datasource actor will
be disconnected(in our case, the initialize type in consctructor is
ColumnBasedRecord). Add new output type class - EML200OutputTypeInitialize, this
output type will do nothing except given a value in construct. So the bug has
been fixed.

Actions
Copy link
 #2

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 2357

Actions
Copy link

Also available in: Atom PDF