maudrid opened a new issue, #27437:
URL: https://github.com/apache/superset/issues/27437

   ### Bug description
   
   When exporting certain datasets, the serialized version of the dataset is 
invalid.
   This causes validation with marshmallow to fail when you try to import it 
again.
   
   
   ### How to reproduce the bug
   
   
   In the superset UI:
   1. Open any dataset
   2. Go to the settings tab and enter any value in the `TEMPLATE PARAMETERS` 
field and save. This is enough to trigger the bug, but you can also remove the 
value from the `TEMPLATE PARAMETERS` field and save again, and the bug will 
still persist.
   3. Export the dataset using the export feature.
   4. Immediately try to import the same dataset again.
   
   ### Screenshots/recordings
   
   
![image](https://github.com/apache/superset/assets/9637747/14fdfbd7-69c3-4a1d-a675-17a2c0b10d42)
   
   
![image](https://github.com/apache/superset/assets/9637747/031af68c-174b-4cd3-a5f8-d5253b14680f)
   
   
   ### Superset version
   
   3.0.4
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   In order to work around this issue:
   1. Open the zip file and extract the dataset yaml file
   2. Find the field called template_params. If the dataset is broken the value 
of this field will be a string value or an empty string like this: 
template_params: ''
   3. Change the value to null like this -> template_params: null
   4. Save the file and place it back into the zip file that was exported.
   5. Import the dataset back into superset
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to