search

apache / superset

Apache Superset is a Data Visualization and Data Exploration Platform
https://superset.apache.org/
Apache License 2.0
62.19k stars 13.65k forks source link

Can't see tables in RedShift that are from datashare #20184

Closed amihaygil closed 7 months ago

amihaygil commented 2 years ago

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Create Redshift cluster with datashare to another cluster.
  2. Run in sqllab (you'll data)
  3. Run in drop-down filter to see schema name (you'll see ) but table filter doesn't work

Expected results

See table list

Actual results

List is empty

Screenshots

If applicable, add screenshots to help explain your problem. image

Environment

(please complete the following information):

version Version: 0.0.0dev

rusackas commented 2 years ago

What driver are you using? We've seen a random uptick in redshift issues, but people seem to be using a variety of drivers to connect.

amihaygil commented 2 years ago

latest we are using pip to install: ... sqlalchemy-redshift \ psycopg2-binary==2.9.1

thinhnd2104 commented 2 years ago

Like #122. datashare metadata is in SVV_DATASHARES. So you can query it but can't see it in table schema.

BhuviTheDataGuy commented 2 years ago

@amihaygil - we are trying to make the connection to a data share. In the database name - We gave the datashare db name, but its throwing error like, use cross-database querying not creating a connection.

How did you connect the datashare db without mentioning the database name in the SQL query?

amihaygil commented 1 year ago

the idea is to map datashare from the sharing side to the shared side ALTER DATASHARE prod_datashare ADD SCHEMA mysql_stats_db_statslmn_stats; -- share from CREATE EXTERNAL SCHEMA prod_mysql_stats_db_statslmn_stats FROM REDSHIFT DATABASE 'prod_dwh' SCHEMA 'mysql_stats_db_statslmn_stats' -- shared to dev ALTER DATASHARE prod_datashare ADD ALL TABLES IN SCHEMA mysql_stats_db_statslmn_stats;

meixikyi commented 1 year ago

@amihaygil hello, did you find some way for this issue?

amihaygil commented 1 year ago

not yet . we are going to work this soon

‫בתאריך יום ג׳, 15 בנוב׳ 2022 ב-5:54 מאת ‪meixikyi‬‏ <‪ @.***‬‏>:‬

@amihaygil https://github.com/amihaygil hello, did you find some way for this issue?

— Reply to this email directly, view it on GitHub https://github.com/apache/superset/issues/20184#issuecomment-1314732227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUTHPLA3DWG3G2B623RPZV3WIMCNDANCNFSM5W4VHFPA . You are receiving this because you were mentioned.Message ID: @.***>

mohrman commented 1 year ago

@amihaygil This is the same for all database tools right? Like DataGrip, DBeaver etc? So it's actually related to the specific table not being accessible in a redshift shared database?

rusackas commented 1 year ago

we are going to work this soon

Let @yousoph , @eschutho or I know if you need any help/input along the way. We look forward to the contribution/resolution!

macsir commented 1 year ago

I got this too in the same account but different clusters. Can't see the shared tables from consumers side. Is there any update or fix? Thanks.

rusackas commented 7 months ago

Hi there, and sorry this has gone quiet for so long. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale. If it is still an issue in Superset 3.x, we can re-open this, or feel free to open a new issue with updated context.