Right "schema access on [my_pg_instance].[my_schema]" of uploaded "CSV to Database" table does not appear in Rights list of roles (PostgreSQL)

[sfkeller]

Expected results

When importing a CSV e.g. to PostgreSQL database (e.g. "my_pg_instance") through menu item "CSV to Database" (path /csvtodatabaseview/form/ ); and when indicating a schema "my_schema" in field "Schema" (=>"Specify a schema ..."). Then when opening menu item "List Roles" (path /roles/list/) the right "schema access on [my_pg_instance].[my_schema]" should appear.

Actual results

What actually happens is, that the newly created schema (e.g. "my_schema") does not appear when trying to assign this schema to another role when editing a role in "List Roles" .

How to reproduce the bug

1. Go to menu "CSV to Database", select a PostgreSQL instance with CSV upload enabled.
2. Click on field 'Schema' and enter schema "my_schema"
3. Go to menu "List Roles", edit a role and try to add "schema access on [my_pg_instance].[my_schema]".
4. "schema access on [my_pg_instance].[my_schema]" does not appear.

Issue is, that the user who just uploaded a CSV into a table can't handle rights on this table.

Environment

• superset version: 0.34
• python version: 3.7
• node.js version: N/A
• npm version: N/A

Checklist

• I have checked the superset logs for python stacktraces 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

We're struggling with a Superset Cloud Instance which is multi-tenant, i.e. where "producers" (roles) only see and share own databases, schemas, charts and dashboards with their "consumers" (roles).

[issue-label-bot]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.73. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[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.

[sfkeller]

Pls. pin this issue. It doesn't make much sense to label a bug as stale.

[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.

[willbarrett]

@rusackas @craig-rueda can you pin this?

[junlincc]

is it still an issue in latest version?

[graceguo-supercat]

close this issue since no recent follow up.