CSV upload for on-premise Hadoop cluster block through erroneous code

[0xBADBAC0N]

Hi guys,
I have the issue that I can not upload a CSV to Hive through Superset as our Hadoop is not running on S3.
I hunted it down to this line in the code: https://github.com/apache/superset/blob/master/superset/db_engine_specs/hive.py#L65
The following settings in the config are all related to the bucket: https://github.com/apache/superset/blob/master/superset/config.py#L781
The issue is my Hive is running on-premise therefore I have no bucket.

Expected results

Uploading a CSV through the frontend should end up putting the file to Hadoop and make it accessible through a table.

Actual results

Uploading the CSV will cause an error like
Unable to upload CSV file "kc_house_data.csv" to table "hendrik_house_test" in database "Hive Production". Error message: No upload bucket specified. You can specify one in the config file.

Screenshots

How to reproduce the bug

1. Go to the main dashboard
2. Click on Data
3. Click on Upload a CSV
4. Enter Table name and Choose file etc
5. Save
6. See error

Environment

• superset version: 1
• python version: Python 3.7.3

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stack traces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

It seems like the current upload functionality does only work as long the related cluster is cloud based. It looks like this bug is only affecting on-premise clusters therefore we would highly appreciate to get this fixed :)

[srinify]

Any helpful tips here @etr2460 ? I know y'all use CSV upload to hive a bit

[0xBADBAC0N]

bump :)

[0xBADBAC0N]

@etr2460 Any idea for this one or even plans? : )
If you would give us some hands we also could start fixing this : )

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[livwel-populus]

Any word on this feature or how to fix it?

[campi01]

Is this even on the radar for getting looked at, or is it not to be supported at all?

[rusackas]

Is this even on the radar for getting looked at, or is it not to be supported at all?

It doesn't seem to be on anyone's radar. Any interest in diagnosing/contributing?

If nobody has interest in picking this up, we might close it as stale before long, as we're trying to steer toward a more actionable backlog of issues.