SQL query not working in Quicksight but working in Athena

Question & Answer
, , , ,
1

I have a dataset (datasource is Athena, and in Athena the datasource is from dynamodb) that is being used in quicksight and the custom sql query is not working in the dataset. When I look at that query in Athena “recent queries”, I see this error.
“GENERIC_INTERNAL_ERROR: java.net.URISyntaxException: Relative path in absolute URI: arn:aws:dynamodb:REGION1:ACCOUNT_NUMBER:table/TABLE_NAME”
now if i rerun that query from Athena, the query works fine. And also if I just run the query in a new query Athena, it works fine and displays the result. It just doesn’t work in quick sight.

Has anyone faced this kind of issue before? any tips on how I can fix it?

2

Hi @haider - Can you check that you had added DynaomoDB service in your QuickSight. You can do it by Manage QuickSight -->Security permission → Manage and add Dyanmo DB.

If the problem persists, you can raise a ticket to AWS Customer support team so that they can see this issue by screen share and advise you the solution. To raise the request, please follow the link - Creating support cases and case management - AWS Support

Regards -Sanjeeb

1 Like
3

Hi @Sanjeeb2022 , I don’t see an option for adding DynamoDB from the list there.

2023-06-08 15_00_29-Edit Resource Permissions
2023-06-08 15_00_29-Edit Resource Permissions710×640 41.5 KB

1 Like
4

Hi @haider - I did not realize that DyanmoDB is NO SQL and it is not listed. I am doubtful whether you can connect dyanmo with QuickSight via athena. Is it possible to unload the data to S3 and create athena table and then point to QuickSight.

In parallel, please raise a ticket to AWS Customer team for this request so that they can see your screen and guide you. In our use case, we unload the data from NO SQL to S3 and then do the reporting. To raise the request, please follow the link -

Regards - Sanjeeb

1 Like
5

@Sanjeeb2022 I am using a connector to get the dynamodb data available in quicksight. here is a link to the process of the setup and I followed it:

3 Likes
6

Thanks @haider . I am also suspecting there should be some intermediate intelligence who did this. Thanks for sharing this link. I will have a look on this. In parallel, please raise a ticket to AWS Customer support to help you on this.

If you are getting any solution, please share to community so that we can learn it as well.

Regards - Sanjeeb

1 Like
7

Hi @haider,

I found a similar question logged in github.

This references this AWS blog which runs through the steps to setup Athena federated query with DynamoDB and visualise data in QuickSight.

Perhaps you can use this to verify that all of the required configuration steps have been completed to setup federation?

Many Thanks,
Andrew

2 Likes
8

Thank you @abacon for sharing this details.

Regards - Sanjeeb

1 Like
9

I was able to run the query in Quicksight when I mention the complete path of the table in FROM
so for example, this query works in Athena:
select * from database1.table1
but it does not work in quicksight. so in quicksight you need to mention the catalog name also, like this:
select * from catalog1.database1.table1
and then the query worked fine. not sure if this is intended to work like this or a bug.

1 Like