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

   ### Bug description
   
   I am encountering an issue while attempting to import a dataset through the 
Superset API within a local Docker container environment. Despite trying 
various solutions, including following suggestions from previous issues and 
referencing external resources such as Stack Overflow 
(https://stackoverflow.com/questions/66015739/use-apache-superset-api-to-feed-a-dataset...),
 I am still unable to resolve the problem.
   
   Additionally, I attempted to upload the file via the Swagger/v1 interface, 
but encountered the same error consistently:
   
   422, superset.commands.exceptions.CommandInvalidError: Could not find a 
valid command to import file
   I have thoroughly reviewed the provided solutions and documentation, 
ensuring that I adhere to the correct request format, data types, and 
authentication procedures. However, the issue persists.
   
   Any assistance or guidance in resolving this matter would be greatly 
appreciated.
   
   
   
   Expected Behavior:
   The dataset should be successfully imported into Superset without 
encountering any errors.
   Actual Behavior:
   Encountering a 422 error with the following message: 
"superset.commands.exceptions.CommandInvalidError: Could not find a valid 
command to import file".
   
   Additional Information:
   
   Operating environment: local Docker container
   Utilized solutions from previous issues and external resources, but to no 
avail.
   Attempted to upload the file via the Swagger/v1 interface, resulting in the 
same error.
   Verified adherence to API documentation, request format, data types, and 
authentication procedures.
   Any assistance or insights into resolving this issue would be highly 
appreciated.
   
   ### How to reproduce the bug
   
   Attempt to import a dataset through the Superset API in a local Docker 
container environment.
   Alternatively, try uploading the file via the Swagger/v1 interface.
   Observe the consistent occurrence of the 422 error along with the associated 
error message.
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] 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