SourceResource field should not be added as a basefield to the Dataset entity. It makes data_pipelines
table grow, if there is a new SourceResource is added. Most of these add columns are empty.
DESCRIBE data_pipelines;
+------------------------+---------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------------------+---------------------+------+-----+---------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| source | varchar(255) | NO | | NULL | |
| uuid | varchar(128) | NO | UNI | NULL | |
| name | varchar(255) | YES | | NULL | |
| pipeline | varchar(255) | YES | MUL | NULL | |
| status | varchar(255) | YES | MUL | NULL | |
| csv_file__target_id | int(10) unsigned | YES | MUL | NULL | |
| csv_file__display | tinyint(3) unsigned | YES | | 1 | |
| csv_file__description | text | YES | | NULL | |
| csv_text | longtext | YES | | NULL | |
| csv_uri__uri | varchar(2048) | YES | MUL | NULL | |
| csv_uri__title | varchar(255) | YES | | NULL | |
| csv_uri__options | longblob | YES | | NULL | |
| json_file__target_id | int(10) unsigned | YES | MUL | NULL | |
| json_file__display | tinyint(3) unsigned | YES | | 1 | |
| json_file__description | text | YES | | NULL | |
| json_text | longtext | YES | | NULL | |
| json_uri__uri | varchar(2048) | YES | MUL | NULL | |
| json_uri__title | varchar(255) | YES | | NULL | |
| json_uri__options | longblob | YES | | NULL | |
| json_path_to_data | varchar(255) | YES | | NULL | |
+------------------------+---------------------+------+-----+---------+----------------+
21 rows in set (0.002 sec)
See the problem statement
Make Dataset entity bundle-able just like media entity in core and allow selecting source resource on bundle creation screen. It will allow
Dataset entity to create source resource field as bundlefield or configurable field.
Dataset entity will be bundle-able
Source resource field is not a basefield.
data_pipelines will not have empty columns.
Closed: won't fix
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.