Does superset supports S3 tables feature in AWS ?

[omkenge]

I tried out to connect with Athena and Superset. I have tables in S3 Tables I did not show any schema
The string which i Used
awsathena+rest://XXX:XX@athena.region.amazonaws.com/db?s3_staging_dir=s3://XXXcatalog_name=s3tablescatalog/bucket_name

[dosubot[bot]]

Hello @omkenge! I'm Dosu, here to assist you with bugs, questions, and contributing. I'm ready to help while you wait for a human maintainer. How can I assist you today?

Yes, Superset supports handling S3 tables in AWS Athena. To ensure proper configuration, you need to set specific environment variables and feature flags:

Environment Variables:

• SUPERSET_REGION: Set this to your AWS region, e.g., eu-west-1.
• SUPERSET_WORKGROUP: Set this to your Athena workgroup, e.g., superset-etl.
• SUPERSET_ATHENA_DB: Set this to your Athena database name, e.g., my_superset_db.

Feature Flags:

• DownloadCSVFromS3: Enable this feature flag (DOWNLOAD_CSV_FROM_S3).
• ShowDefaultCSVOptions: Enable this feature flag (SHOW_DEFAULT_CSV_OPTIONS) ^[1].

Additionally, ensure that your connection string is correctly formatted and includes all necessary parameters. The format should be:

awsathena+rest://{aws_access_key_id}:{aws_secret_access_key}@athena.{region_name}.amazonaws.com/{schema_name}?s3_staging_dir={s3_staging_dir}&...

If you are experiencing schema visibility issues, common causes include incorrect schema names or insufficient permissions. Verify that the schema exists and that your user account has the necessary permissions ^[2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[omkenge]

Is there any issue with lake formation any body faced from AWS ? building with connection string

[alexFuseit]

Did you manage to find a solution to this problem @omkenge ? Also facing similar issue