Body
This issue summarizes several problems in the dataset CSV import flow:
-
Preview overflow:
The preview table in step 2 does not support horizontal scrolling. When the dataset exceeds the component width, some columns are not accessible.
-
Property scope handling:
When importing data into an existing dataset, the property scope should be automatically selected based on the target dataset. Currently, users can change it, which should not be allowed.
-
Data type validation:
There is no proper handling of type mismatches between the CSV and the existing dataset schema. This is especially relevant for dimension properties, e.g., when values are stored as strings ("1", "2") but provided as numeric values in the CSV.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.
Body
This issue summarizes several problems in the dataset CSV import flow:
Preview overflow:
The preview table in step 2 does not support horizontal scrolling. When the dataset exceeds the component width, some columns are not accessible.
Property scope handling:
When importing data into an existing dataset, the property scope should be automatically selected based on the target dataset. Currently, users can change it, which should not be allowed.
Data type validation:
There is no proper handling of type mismatches between the CSV and the existing dataset schema. This is especially relevant for dimension properties, e.g., when values are stored as strings (
"1","2") but provided as numeric values in the CSV.StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.