You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @xingyuli, thanks for reporting the issue!
I'm not familiar with this functionality - edit dataset via the rest PUT api. While I loop the domain expert in, would you mind giving some more details 1) your use case 2) is there a workaround that you may be aware of? thanks
Hi @xingyuli, thanks for reporting the issue! I'm not familiar with this functionality - edit dataset via the rest PUT api. While I loop the domain expert in, would you mind giving some more details 1) your use case 2) is there a workaround that you may be aware of? thanks
The rest PUT API has been used to sync from one dataset to another dataset. These two datasets refer two tables which are created by absolutely same ddl statement. You may think of these datasets as blue-green (or prod-vs-backup) version against each other. I have so many datasets created via the GUI, but I wish to programmatically maintain the plenty of datasets.
As it's not possible to specify the metric's label (verbose_name) via the API, I have to update them one by one, going through all the datasets, which is quite time consuming and inconvenient. As far as I see, I think there is no workaround to do this.
For wider insight, Superset is missing features of sync one set of datasets to another set of datasets, which would be useful for cases e.g.,
blue-green dataset
full dataset and its hot dataset (which means a subset of whole dataset)
It's not possible to update dataset metric's label (i.e., verbose_name) via the PUT API.
How to reproduce the bug
Visit the online rest documentation. You could see the payload is not able to receive verbose_name:
Expected results
Possible to update the metric label (verbose_name).
Actual results
Unable to do so.
Screenshots
See above.
Environment
(please complete the following information):
The text was updated successfully, but these errors were encountered: