Revision 36989
Added by Marek Horst about 9 years ago
| workflow.xml | ||
|---|---|---|
| 50 | 50 |
<name>input_project_statistics</name> |
| 51 | 51 |
<value>$UNDEFINED$</value> |
| 52 | 52 |
</property> |
| 53 |
<property> |
|
| 54 |
<name>input_document_websiteusage_similarity</name> |
|
| 55 |
<value>$UNDEFINED$</value> |
|
| 56 |
</property> |
|
| 53 | 57 |
<!-- entities exporting modes --> |
| 54 | 58 |
<property> |
| 55 | 59 |
<name>active_export_referenceddataset_datasets</name> |
| ... | ... | |
| 242 | 246 |
<name>input_project_statistics</name> |
| 243 | 247 |
<value>${input_project_statistics}</value>
|
| 244 | 248 |
</property> |
| 249 |
<property> |
|
| 250 |
<name>input_document_websiteusage_similarity</name> |
|
| 251 |
<value>${input_document_websiteusage_similarity}</value>
|
|
| 252 |
</property> |
|
| 245 | 253 |
<!-- action managed related --> |
| 246 | 254 |
<property> |
| 247 | 255 |
<name>action_hbase_table_name</name> |
Also available in: Unified diff
#118 explicitly defining input_document_websiteusage_similarity parameter. This is not a bug fix because exporter works properly without explicitly defining input port due to propagate-configuration mode but we should have all input port definitions aligned to avoid confusions.